Results 1 to 6 of 6

Thread: UDP issue...

  1. #1

    UDP issue...

    Ok, it looks like there is no solution to this problem and I am completely, but really completely lost.

    As I previously said, we are hosting a battle.net server but since we are with Layeredtech.com, many users got some UDP issues.

    The battle.net server
    We tested it on 2 different servers and those users had no UDP errors so the problem is not our battle.net server. We even tried few other versions of battle.net server on layeredtech.com to make sure that it wasn't our version and it was the same: The same users were having the same UDP error.

    The OS
    The OS of the 2 other server where we tested our battle.net server were on redHat 9 but on layeredtech.com we had FreeBSD 5.2.1 as OS so layeredtech.com highly suggested us to change OS to redHat 9 which I did. It cost me $50 for nothing since it fixed nothing. Same UDP error for the same users.

    The Network
    Then layeredtech.com suggested us to switch network from saavis to The Planet Network since that on The Planet Network there is no ports blocked at all. This time, I really though it would do it and fix it but sadly.... same UDP error for the same users...

    So we are completely lost. The battle.net software is not the problem, we changed the OS and we even changed the network and the same users still get the same UDP error...

    The thing is that these users are using some routers and/or firewall BUT they have no problems to play on any other battle.net servers available out there except ours SINCE we moved to layeredtech.com. And if we put our battle.net server on another server (such as servint.net, which we tested it on), no one got any UDP error.

    What on Layeredtech.com could block some users while appropriate port (6112 UDP/TCP) is wide open?? There is no firewall or anything like that but some users still got blocked.

    By the way, our ns1 and ns2 are redirected to our own dedicated IP. That is fine right?

    I have no complaints to say about layeredtech.com because they are giving some great help from the start but the problem is that I begin to wonder if there is really a solution beside moving to another server.

    The thing is that I do not want to move because they are just EXCELLENT and I have some bad experiences with some other hosts and beside that UDP "bug" we are very happy with them. The thing though is that we are there for one month already and we stuck and cannot open our service yet...

    If someone got an idea/solution... There is no words to express how much grateful I would be.

  2. #2
    SOmeone suggested me to use this command and here are the results:

    root@defoy [~]# tcpdump -l -nn host 217.211.137.243
    tcpdump: listening on eth0
    13:01:20.673724 217.211.137.243.65477 > 69.93.215.69.6112: S 1397943048:1397943048(0) win 65535 <mss 1460,nop,nop,sackOK> (DF)
    13:01:20.673755 69.93.215.69.6112 > 217.211.137.243.65477: S 797360103:797360103(0) ack 1397943049 win 5840 <mss 1460,nop,nop,sackOK> (DF)
    13:01:20.835774 217.211.137.243.65477 > 69.93.215.69.6112: . ack 1 win 65535 (DF)
    13:01:20.849573 217.211.137.243.65477 > 69.93.215.69.6112: P 1:2(1) ack 1 win 65535 (DF)
    13:01:20.849587 69.93.215.69.6112 > 217.211.137.243.65477: . ack 2 win 5840 (DF)
    13:01:21.012332 217.211.137.243.65477 > 69.93.215.69.6112: P 2:53(51) ack 1 win 65535 (DF)
    13:01:21.012345 69.93.215.69.6112 > 217.211.137.243.65477: . ack 53 win 5840 (DF)
    13:01:21.012399 69.93.215.66.6112 > 217.211.137.243.6112: udp 8 (DF)
    13:01:21.012405 69.93.215.66.6112 > 217.211.137.243.6112: udp 8 (DF)
    13:01:21.012470 69.93.215.69.6112 > 217.211.137.243.65477: P 1:9(8) ack 53 win 5840 (DF)
    13:01:21.175920 217.211.137.243.65477 > 69.93.215.69.6112: P 53:61(8) ack 9 win 65527 (DF)
    13:01:21.175952 69.93.215.69.6112 > 217.211.137.243.65477: P 9:110(101) ack 61 win 5840 (DF)
    13:01:21.338858 217.211.137.243.51414 > 69.93.215.69.6112: udp 12
    13:01:21.338959 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.338966 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.340114 217.211.137.243.51414 > 69.93.215.69.6112: udp 12
    13:01:21.340157 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.340163 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.340942 217.211.137.243.51414 > 69.93.215.69.6112: udp 12
    13:01:21.340982 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.340989 69.93.215.66.6112 > 217.211.137.243.51414: udp 8 (DF)
    13:01:21.415134 217.211.137.243.65477 > 69.93.215.69.6112: P 61:169(108) ack 110 win 65426 (DF)
    13:01:21.415247 69.93.215.69.6112 > 217.211.137.243.65477: P 110:119(9) ack 169 win 5840 (DF)
    13:01:21.504329 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.505195 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.507120 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.508226 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.509412 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.510394 217.211.137.243 > 69.93.215.66: icmp: 217.211.137.243 udp port 51414 unreachable
    13:01:21.577259 217.211.137.243.65477 > 69.93.215.69.6112: P 169:173(4) ack 119 win 65417 (DF)
    13:01:21.577369 69.93.215.69.6112 > 217.211.137.243.65477: P 119:146(27) ack 173 win 5840 (DF)
    13:01:21.746053 217.211.137.243.65477 > 69.93.215.69.6112: P 173:667(494) ack 146 win 65390 (DF)
    13:01:21.746127 69.93.215.69.6112 > 217.211.137.243.65477: P 146:181(35) ack 667 win 6432 (DF)
    13:01:22.033894 217.211.137.243.65477 > 69.93.215.69.6112: . ack 181 win 65355 (DF)
    13:01:22.033909 69.93.215.69.6112 > 217.211.137.243.65477: P 181:317(136) ack 667 win 6432 (DF)
    13:01:22.334195 217.211.137.243.65477 > 69.93.215.69.6112: . ack 317 win 65219 (DF)
    13:01:25.085811 217.211.137.243.65477 > 69.93.215.69.6112: P 667:707(40) ack 317 win 65219 (DF)
    13:01:25.087335 69.93.215.69.6112 > 217.211.137.243.65477: P 317:325(8) ack 707 win 6432 (DF)
    13:01:25.361719 217.211.137.243.65477 > 69.93.215.69.6112: P 707:720(13) ack 325 win 65211 (DF)
    13:01:25.362397 69.93.215.69.6112 > 217.211.137.243.65477: P 325:350(25) ack 720 win 6432 (DF)
    13:01:25.525024 217.211.137.243.65477 > 69.93.215.69.6112: P 720:746(26) ack 350 win 65186 (DF)
    13:01:25.525158 69.93.215.69.6112 > 217.211.137.243.65477: P 350:516(166) ack 746 win 6432 (DF)
    13:01:25.838964 217.211.137.243.65477 > 69.93.215.69.6112: . ack 516 win 65020 (DF)
    13:01:25.838979 69.93.215.69.6112 > 217.211.137.243.65477: P 516:1667(1151) ack 746 win 6432 (DF)
    13:01:26.139312 217.211.137.243.65477 > 69.93.215.69.6112: . ack 1667 win 65535 (DF)
    13:01:26.340657 217.211.137.243.65477 > 69.93.215.69.6112: P 746:766(20) ack 1667 win 65535 (DF)
    13:01:26.340854 69.93.215.69.6112 > 217.211.137.243.65477: P 1667:1723(56) ack 766 win 6432 (DF)
    13:01:26.504099 217.211.137.243.65477 > 69.93.215.69.6112: P 766:784(18) ack 1723 win 65479 (DF)
    13:01:26.540021 69.93.215.69.6112 > 217.211.137.243.65477: . ack 784 win 6432 (DF)
    13:01:32.860076 69.93.215.69.6112 > 217.211.137.243.65477: P 1723:1731(8) ack 784 win 6432 (DF)
    13:01:33.026333 217.211.137.243.65477 > 69.93.215.69.6112: P 784:792(8) ack 1731 win 65471 (DF)
    13:01:33.026349 69.93.215.69.6112 > 217.211.137.243.65477: . ack 792 win 6432 (DF)
    13:01:33.027124 69.93.215.69.6112 > 217.211.137.243.65477: P 1731:1772(41) ack 792 win 6432 (DF)
    13:01:33.350926 217.211.137.243.65477 > 69.93.215.69.6112: . ack 1772 win 65430 (DF)

    Looks like port 51414 is blocked but our host is saying that everything is open BUT they say:
    We do not block any ports on our end, but our servers by default have unused ports turned off (as a security measure). Try opening the port on your end, and let us know if it's still an issue.

    Stupid question but... how do we open ports with SSH? I never did a such thing. Personnally I would like to open them all except those who have some security issues. So second question is, which ones should I leave closed exactly?

    Thanks

  3. #3
    Originally posted by killer15669

    Looks like port 51414 is blocked but our host is saying that everything is open BUT they say:
    We do not block any ports on our end, but our servers by default have unused ports turned off (as a security measure). Try opening the port on your end, and let us know if it's still an issue.

    Stupid question but... how do we open ports with SSH? I never did a such thing. Personnally I would like to open them all except those who have some security issues. So second question is, which ones should I leave closed exactly?

    Thanks [/B]
    Login to your server and to this
    iptables -L

    Notice that is an upper case L. If there any ports blocked there
    that would show it. Also they might be talking about /etc/services
    and I am not sure if that would efect your game server because that is just not my thing so I don't know much about them, I would not think that /etc/services not having an entery for that port would cause a problem but who knows.
    The Web Space Place: Good Service No Contracts

    http://www.thewebspaceplace.net

  4. #4
    Join Date
    Nov 2001
    Location
    Ann Arbor, MI
    Posts
    2,979
    It appears that the client is refusing the connections to UDP port 51414, not the server. If the server is the 69.93.215.69 IP address.

    What's a dump look like on a client that works?
    -Mark Adams
    www.bitserve.com - Secure Michigan web hosting for your business.
    Only host still offering a full money back uptime guarantee and prorated refunds.
    Offering advanced server management and security incident response!

  5. #5
    I already did a # iptables -F (and /etc/init.d/iptables stop) and # iptables -L:

    root@defoy [~]# iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    acctboth all -- anywhere anywhere

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination
    acctboth all -- anywhere anywhere

    Chain acctboth (2 references)
    target prot opt source destination
    tcp -- defoy.pgtour.net anywhere tcp dpt:http
    tcp -- anywhere defoy.pgtour.net tcp spt:http
    tcp -- defoy.pgtour.net anywhere tcp dptmtp
    tcp -- anywhere defoy.pgtour.net tcp sptmtp
    tcp -- defoy.pgtour.net anywhere tcp dpt:pop3
    tcp -- anywhere defoy.pgtour.net tcp spt:pop3
    icmp -- defoy.pgtour.net anywhere
    icmp -- anywhere defoy.pgtour.net
    tcp -- defoy.pgtour.net anywhere
    tcp -- anywhere defoy.pgtour.net
    udp -- defoy.pgtour.net anywhere
    udp -- anywhere defoy.pgtour.net
    all -- defoy.pgtour.net anywhere
    all -- anywhere defoy.pgtour.net
    tcp -- 69.93.215.67 anywhere tcp dpt:http
    tcp -- anywhere 69.93.215.67 tcp spt:http
    tcp -- 69.93.215.67 anywhere tcp dptmtp
    tcp -- anywhere 69.93.215.67 tcp sptmtp
    tcp -- 69.93.215.67 anywhere tcp dpt:pop3
    tcp -- anywhere 67.69-93-215.reverse.theplanet.comtcp spt:pop3
    icmp -- 67.69-93-215.reverse.theplanet.com anywhere
    icmp -- anywhere 67.69-93-215.reverse.theplanet.com
    tcp -- 67.69-93-215.reverse.theplanet.com anywhere
    tcp -- anywhere 67.69-93-215.reverse.theplanet.com
    udp -- 67.69-93-215.reverse.theplanet.com anywhere
    udp -- anywhere 67.69-93-215.reverse.theplanet.com
    all -- 67.69-93-215.reverse.theplanet.com anywhere
    all -- anywhere 67.69-93-215.reverse.theplanet.com
    tcp -- mail11.biplexic.com anywhere tcp dpt:http
    tcp -- anywhere mail11.biplexic.comtcp spt:http
    tcp -- mail11.biplexic.com anywhere tcp dptmtp
    tcp -- anywhere mail11.biplexic.comtcp sptmtp
    tcp -- mail11.biplexic.com anywhere tcp dpt:pop3
    tcp -- anywhere mail11.biplexic.comtcp spt:pop3
    icmp -- mail11.biplexic.com anywhere
    icmp -- anywhere mail11.biplexic.com
    tcp -- mail11.biplexic.com anywhere
    tcp -- anywhere mail11.biplexic.com
    udp -- mail11.biplexic.com anywhere
    udp -- anywhere mail11.biplexic.com
    all -- mail11.biplexic.com anywhere
    all -- anywhere mail11.biplexic.com
    tcp -- mail13.biplexic.com anywhere tcp dpt:http
    tcp -- anywhere mail13.biplexic.comtcp spt:http
    tcp -- mail13.biplexic.com anywhere tcp dptmtp
    tcp -- anywhere mail13.biplexic.comtcp sptmtp
    tcp -- mail13.biplexic.com anywhere tcp dpt:pop3
    tcp -- anywhere mail13.biplexic.comtcp spt:pop3
    icmp -- mail13.biplexic.com anywhere
    icmp -- anywhere mail13.biplexic.com
    tcp -- mail13.biplexic.com anywhere
    tcp -- anywhere mail13.biplexic.com
    udp -- mail13.biplexic.com anywhere
    udp -- anywhere mail13.biplexic.com
    all -- mail13.biplexic.com anywhere
    all -- anywhere mail13.biplexic.com
    tcp -- mail12.biplexic.com anywhere tcp dpt:http
    tcp -- anywhere mail12.biplexic.comtcp spt:http
    tcp -- mail12.biplexic.com anywhere tcp dptmtp
    tcp -- anywhere mail12.biplexic.comtcp sptmtp
    tcp -- mail12.biplexic.com anywhere tcp dpt:pop3
    tcp -- anywhere mail12.biplexic.comtcp spt:pop3
    icmp -- mail12.biplexic.com anywhere
    icmp -- anywhere mail12.biplexic.com
    tcp -- mail12.biplexic.com anywhere
    tcp -- anywhere mail12.biplexic.com
    udp -- mail12.biplexic.com anywhere
    udp -- anywhere mail12.biplexic.com
    all -- mail12.biplexic.com anywhere
    all -- anywhere mail12.biplexic.com
    all -- anywhere anywhere

    Nevertheless, I got this earlier:




    Results for tcpdump -l -nn udp:
    WITH UDP ERROR
    19:26:02.379399 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.379407 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.700094 216.39.178.13.6112 > 69.93.215.69.6112: udp 12
    19:26:02.700197 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.700205 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.701362 216.39.178.13.6112 > 69.93.215.69.6112: udp 12
    19:26:02.701406 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.701413 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.702284 216.39.178.13.6112 > 69.93.215.69.6112: udp 12
    19:26:02.702325 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)
    19:26:02.702332 69.93.215.66.6112 > 216.39.178.13.6112: udp 8 (DF)

    #2

    root@defoy [~]# tcpdump -l -nn udp
    tcpdump: listening on eth0
    22:18:26.688203 69.93.215.66.6112 > 65.94.196.56.6112: udp 8 (DF)
    22:18:26.688211 69.93.215.66.6112 > 65.94.196.56.6112: udp 8 (DF)
    22:18:26.807387 65.94.196.56.51414 > 69.93.215.69.6112: udp 12
    22:18:26.807466 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:26.807472 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:26.812436 65.94.196.56.51414 > 69.93.215.69.6112: udp 12
    22:18:26.812480 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:26.812486 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:26.817805 65.94.196.56.51414 > 69.93.215.69.6112: udp 12
    22:18:26.817848 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:26.817854 69.93.215.66.6112 > 65.94.196.56.51414: udp 8 (DF)
    22:18:34.050728 24.84.124.182.6112 > 69.93.215.69.6112: udp 8




    NO UDP ERROR
    19:42:10.457905 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.457915 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.572397 24.37.204.126.6112 > 69.93.215.69.6112: udp 12
    19:42:10.572449 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.572456 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.577134 24.37.204.126.6112 > 69.93.215.69.6112: udp 12
    19:42:10.577176 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.577183 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.580602 24.37.204.126.6112 > 69.93.215.69.6112: udp 12
    19:42:10.580644 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)
    19:42:10.580650 69.93.215.66.6112 > 24.37.204.126.6112: udp 8 (DF)

    I think I am beginning to believe in magic. And if its the user that are refusing connection on port 51414, why are they getting this UDP error ONLY on our battle.net server?

  6. #6
    Join Date
    Nov 2001
    Location
    Ann Arbor, MI
    Posts
    2,979
    Somehow, those dumps don't look like the first one in this thread.

    tcpdump -l -nn host 217.211.137.243

    Try that where the host is one that works.
    -Mark Adams
    www.bitserve.com - Secure Michigan web hosting for your business.
    Only host still offering a full money back uptime guarantee and prorated refunds.
    Offering advanced server management and security incident response!

Posting Permissions

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