Jump to content

TakeSkate

Inactive Member
  • Posts

    1
  • Joined

  • Last visited

  • Feedback

    0%

About TakeSkate

Informations

  • Gender
    Male
  • Country
    Spain
  • Nationality
    Spanish

TakeSkate's Achievements

Apprentice

Apprentice (3/16)

  • Conversation Starter
  • One Year In
  • One Month Later
  • Week One Done
  • Dedicated

Recent Badges

0

Reputation

  1. Hi, first of all sorry for my bad english. I can read English but I rarely have to write it. i have 1 problem with VM server, i open mt2 ports on router to vm ip ( 192.168.2.19 ) VM ipv4: 192.168.2.19 Windows ipv4: 192.168.2.4 Router public ipv4: 90.2.161.61 (not real only example) i configure Auth, Channel1, Game99 CONFIG file with this: BIND_IP: 192.168.2.19 PROXY_IP: 90.2.161.61 then i edit serverinfo.py compile root.eix/epk and sent the client to my mates SERVER_NAME = "Metin2" SERVER_NAME_TEST = "Test" SERVER_IP = "90.2.161.61" SERVER_IP_TEST = "127.0.0.1" CH1_NAME = "CH1" CH2_NAME = "CH2" CH3_NAME = "CH3" CH4_NAME = "CH4" PORT_1 = 13000 PORT_2 = 13010 PORT_3 = 13020 PORT_4 = 13030 PORT_AUTH = 11000 PORT_MARK = 13000 they can login (auth), select player join in the game and play but i can´t since i use PROXY_IP in CONFIG file i can login (auth), select player and then back me too select server screen then i start the server with CH1 and CH2 open But in CH2 CONFIG file i have this: BIND_IP: 192.168.2.19 #PROXY_IP: Your Public/External IPv4 address my serverinfo.py (for me) have this: SERVER_NAME = "Metin2" SERVER_NAME_TEST = "Test" SERVER_IP = "192.168.2.19" SERVER_IP_TEST = "127.0.0.1" CH1_NAME = "CH1" CH2_NAME = "CH2" CH3_NAME = "CH3" CH4_NAME = "CH4" PORT_1 = 13000 PORT_2 = 13010 PORT_3 = 13020 PORT_4 = 13030 PORT_AUTH = 11000 PORT_MARK = 13000 and this works, but my quest is how can i play with my friends in the same channel?? sysser from client is empty syslog from auth when i try login in ch1: Oct 25 02:15:10 :: SYSTEM: new connection from [192.168.2.4] fd: 16 handshake 2735630493 output input_len 0, ptr 0x21210700 Oct 25 02:15:10 :: Handshake: lower than zero -1 Oct 25 02:15:10 :: Handshake: client_time 0 server_time 997642 Oct 25 02:15:10 :: AUTH_PHASE 0x21210700 Oct 25 02:15:10 :: InputAuth::Login : admin(5) desc 0x21210700 Oct 25 02:15:10 :: SetLoginKey 314022092 Oct 25 02:15:10 :: InputAuth::Login : key 314022092:0x5fbcff0e login admin Oct 25 02:15:10 :: QID_AUTH_LOGIN: START 314022092 0x21210700 Oct 25 02:15:10 :: Create_Time 0 19700101 Oct 25 02:15:10 :: Block Time -2 Oct 25 02:15:10 :: SetRemainSecs admin 0 type 2 Oct 25 02:15:10 :: SendAuthLogin admin key 1 Oct 25 02:15:11 :: AuthLogin result 1 key 314022092 Oct 25 02:15:11 :: SYSTEM: closing socket. DESC #16 looks good i guess, i pass to player select ch1 syslog: Oct 25 02:15:11 :: SYSTEM: new connection from [192.168.2.4] fd: 21 handshake 2100847653 output input_len 0, ptr 0x21ed4980 Oct 25 02:15:11 :: Handshake: client_time 0 server_time 991291 Oct 25 02:15:11 :: LOGIN_BY_KEY: admin key 314022092 Oct 25 02:15:11 :: LoginSuccess Oct 25 02:15:11 :: player([SA]Admin).job(0) Oct 25 02:15:11 :: player().job(0) Oct 25 02:15:11 :: player().job(0) Oct 25 02:15:11 :: player().job(0) Oct 25 02:15:11 :: success to 90.2.161.61:13002 Oct 25 02:15:11 :: InputDB::login_success: admin Oct 25 02:15:11 :: SYSTEM: new connection from [192.168.2.4] fd: 23 handshake 3759863855 output input_len 0, ptr 0x21ed4d00 Oct 25 02:15:12 :: MARK_SERVER: Login Oct 25 02:15:12 :: LargePacket Size 4 Oct 25 02:15:12 :: MARK_SERVER: GuildMarkIDXList 11 bytes sent. Oct 25 02:15:12 :: MARK_SERVER: Sending blocks. (imgIdx 0 diff 0 size 10) Oct 25 02:15:12 :: SYSTEM: closing socket. DESC #23 Oct 25 02:15:15 :: SYSTEM: closing socket. DESC #21 Oct 25 02:15:19 :: SYSTEM: new connection from [192.168.2.4] fd: 21 handshake 3502898768 output input_len 0, ptr 0x21ed4980 Oct 25 02:15:19 :: SYSTEM: closing socket. DESC #21 looks like if the server resend my own traffic to my public ipv4 when i choose player this is normal? how can i fix that?
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.