Page 1 of 2 12 LastLast
Results 1 to 10 of 14
  1. #1
    Newbie
    Join Date
    Nov 2019
    Posts
    10

    Default Steam Game Server

    Trying to setup a dedicated Steam game server. On my old router all I had to do was setup my port forwarding. This is not working. I can see the server as a LAN game but never registers with the Steam servers. I do have a VLAN configuration and the server is on native Internal. Even tried added Bypass Rules and Access Rules under advanced. I have rebooted many time with no avail. When I go to reports I see the ports working everywhere except for the port forward sessions. All is see is when I try it from inside my LAN. Nothing from outside.
    Attached Images Attached Images

  2. #2
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    24,959

    Default

    Basically, it means your forward rule is incorrect. There is no magic difference with Untangle relative to anything else, if you duplicate the forward you had before, the server will work.

    One thing I'll suggest right off the bat... The "new port" field should be EMPTY, seriously... never put anything in that box.

    I'd like to help more, but I'm not sure what game you're talking about. This isn't a "steam" server, it's a game's server... what is it?

    *Edit*, the docs look like standard HL2 stuff... and as usual are wrong. You need ONE THING, and one thing forwarded for a source server. UDP 27015 Now, it looks like UDP 7777 is also used for something... so you might need that too. But to help further I need a screen grab of the actual rules you've made.
    Last edited by sky-knight; 12-22-2019 at 06:45 PM.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  3. #3
    Newbie
    Join Date
    Nov 2019
    Posts
    10

    Default

    The specific Steam game is "The Isle". the port setting are in this how to.

    With My old D-Link Router it simply just work as the document stated. I upgraded to Untangle as my router and now I can only seem to see the game as LAN.
    Attached Images Attached Images

  4. #4
    Newbie
    Join Date
    Nov 2019
    Posts
    10

    Default

    I need to have 5 or more post to share the link

  5. #5

  6. #6
    Untangler jcoffin's Avatar
    Join Date
    Aug 2008
    Location
    Sunnyvale, CA
    Posts
    9,015

    Default

    Access rule changes are not needed. The port forward rules look correct. I would use packet test to see if the packets are making it to the host behind the Untangle /admin/index.do#config/network/troubleshooting/packet
    Attention: Support and help on the Untangle Forums is provided by
    volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

  7. #7
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    24,959

    Default

    I can confirm the rules you've posted are correct when compared to the provided documentation, they are also over-matching and exposing you to risk you don't need to assume... but they are correct enough to ensure the game server is accessible.

    I say over matching because these directions are generic for Steam based services, and built on top of what Half-Life 2 established ages ago. You could probably safely remove TCP from your rules... but if you care about that stuff, do it AFTER you get it working. It's much easier to tune something that's working obviously.

    As JCoffin indicates, no access rule changes are required, and indeed are dangerous to add, so nuke those if you've done that.

    The only thing left is to confirm the new IP address is correct. And, if that static address is correct, 192.168.2.3, I assume Untangle's address on Internal is 192.168.2.1? Is 2.3 using a static configuration? Is its default gateway set to 2.1?
    Last edited by sky-knight; 12-23-2019 at 04:18 PM.
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  8. #8
    Newbie
    Join Date
    Nov 2019
    Posts
    10

    Default

    Yes i see port on the internal side leaving, then on the external side coming into the untangle server.

    Mon Dec 23 2019 18:20:51 GMT-0500 (Eastern Standard Time) - Test Started
    tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes

    18:21:38.136629 IP 192.168.0.3.7780 > 162.254.193.47.27019: UDP, length 36
    18:21:38.136682 IP 192.168.0.3.7780 > 162.254.193.6.27019: UDP, length 36
    18:21:38.136686 IP 192.168.0.3.7780 > 162.254.193.7.27019: UDP, length 36
    18:21:38.136706 IP 192.168.0.3.7780 > 162.254.193.46.27019: UDP, length 36
    18:21:38.142326 IP 192.168.0.3.7780 > 205.196.6.67.27019: UDP, length 36
    18:21:38.142413 IP 192.168.0.3.7780 > 162.254.195.67.27019: UDP, length 36
    18:21:38.175900 IP 162.254.193.46.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.176054 IP 162.254.193.7.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.176359 IP 162.254.193.47.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.191175 IP 192.168.0.3.7780 > 162.254.192.100.27019: UDP, length 36
    18:21:38.191230 IP 192.168.0.3.7780 > 162.254.195.83.27019: UDP, length 36
    18:21:38.191253 IP 192.168.0.3.7780 > 162.254.195.82.27019: UDP, length 36
    18:21:38.191322 IP 192.168.0.3.7780 > 162.254.195.66.27019: UDP, length 36
    18:21:38.201575 IP 162.254.193.6.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.236014 IP 205.196.6.67.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.240494 IP 192.168.0.3.7780 > 205.196.6.75.27019: UDP, length 36
    18:21:38.253459 IP 162.254.192.100.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.253467 IP 162.254.195.67.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.280016 IP 162.254.195.83.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.283302 IP 162.254.195.82.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.285730 IP 162.254.195.66.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.289200 IP 192.168.0.3.7780 > 162.254.192.109.27019: UDP, length 36
    18:21:38.289429 IP 192.168.0.3.7780 > 155.133.254.132.27019: UDP, length 36
    18:21:38.317918 IP 162.254.192.109.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.338406 IP 192.168.0.3.7780 > 162.254.192.108.27019: UDP, length 36
    18:21:38.338471 IP 192.168.0.3.7780 > 155.133.254.133.27019: UDP, length 36
    18:21:38.338600 IP 192.168.0.3.7780 > 162.254.192.101.27019: UDP, length 36
    18:21:38.343240 IP 205.196.6.75.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.346714 IP 155.133.254.132.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.365514 IP 162.254.192.108.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.366842 IP 162.254.192.101.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.387259 IP 192.168.0.3.7780 > 162.254.196.67.27019: UDP, length 36
    18:21:38.387481 IP 192.168.0.3.7780 > 162.254.196.84.27019: UDP, length 36
    18:21:38.395799 IP 155.133.254.133.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.436287 IP 192.168.0.3.7780 > 155.133.248.53.27019: UDP, length 36
    18:21:38.436579 IP 192.168.0.3.7780 > 162.254.196.68.27019: UDP, length 36
    18:21:38.436743 IP 192.168.0.3.7780 > 162.254.196.83.27019: UDP, length 36
    18:21:38.485477 IP 192.168.0.3.7780 > 155.133.248.51.27019: UDP, length 36
    18:21:38.485722 IP 192.168.0.3.7780 > 155.133.248.52.27019: UDP, length 36
    18:21:38.485952 IP 192.168.0.3.7780 > 155.133.248.50.27019: UDP, length 36
    18:21:38.490311 IP 162.254.196.84.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.513940 IP 162.254.196.67.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.534425 IP 192.168.0.3.7780 > 185.25.182.77.27019: UDP, length 36
    18:21:38.534604 IP 192.168.0.3.7780 > 185.25.182.76.27019: UDP, length 36
    18:21:38.537437 IP 162.254.196.68.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.537472 IP 162.254.196.83.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.589118 IP 155.133.248.53.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.595133 IP 155.133.248.50.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.596837 IP 155.133.248.52.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.638459 IP 185.25.182.77.27019 > 192.168.0.3.7780: UDP, length 44
    18:21:38.638873 IP 185.25.182.76.27019 > 192.168.0.3.7780: UDP, length 44
    Mon Dec 23 2019 18:22:53 GMT-0500 (Eastern Standard Time) - Test Completed

  9. #9
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    24,959

    Default

    Whoa... hold up...

    That's coming from 192.168.0.3. The rule says 192.168.2.3. Those aren't the same...

    Are the client and server not on the same IP network? Do you have two internal LANs?
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  10. #10
    Newbie
    Join Date
    Nov 2019
    Posts
    10

    Default

    My modem gives untangle 192.168.0.3. My windows game server is 192.168.2.3

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2