Hey, so I'm putting up a tf2 server in linux for the first time, it's on a vm and it all works perfectly. Now the problem is that when I try to port forward it (everything is set to on 27015), it'll give me a connection refused if I try to connect from the outside.
So the console tells me it's running on 27015, I have 2 routers, one forwards to another that forwards to the vm, it works I've done it with the http server, now, with the tf2 server is a different story, it works on lan, can connect and everything, manage it through the screen command whenever I want to. sv_lan is set to 0.
Thing is it gives me this 127.0.1.1 internal IP, I really don't remember that happening when I did it on windows. The actual machine's ip is 192.168.88.220. So what is happening here? I don't know why I feel like "-ip" wouldn't do much for me but I might try it when I get home.
The the external IP is correct.
The VM is in bridged adapter mode so there should be no need to do anything else.
I have checked everything a lot of times so I don't really get it.
Now that I think of it it might be the screen thing, as 127.0.0.1 is the loopback IP maybe screen is running the server like a vm inside the vm it already is, but then again that would make no sense since I can connect to the server through 192.168.88.22. So if it's available internally why wouldn't it be from the outside if the ports are forwarded?
Welp.
Working linux server not port forwarding.
posted in
Q/A Help
Hey, so I'm putting up a tf2 server in linux for the first time, it's on a vm and it all works perfectly. Now the problem is that when I try to port forward it (everything is set to on 27015), it'll give me a connection refused if I try to connect from the outside.
So the console tells me it's running on 27015, I have 2 routers, one forwards to another that forwards to the vm, it works I've done it with the http server, now, with the tf2 server is a different story, it works on lan, can connect and everything, manage it through the screen command whenever I want to. sv_lan is set to 0.
Thing is it gives me this 127.0.1.1 internal IP, I really don't remember that happening when I did it on windows. The actual machine's ip is 192.168.88.220. So what is happening here? I don't know why I feel like "-ip" wouldn't do much for me but I might try it when I get home.
The the external IP is correct.
The VM is in bridged adapter mode so there should be no need to do anything else.
I have checked everything a lot of times so I don't really get it.
Now that I think of it it might be the screen thing, as 127.0.0.1 is the loopback IP maybe screen is running the server like a vm inside the vm it already is, but then again that would make no sense since I can connect to the server through 192.168.88.22. So if it's available internally why wouldn't it be from the outside if the ports are forwarded?
Welp.
So the console tells me it's running on 27015, I have 2 routers, one forwards to another that forwards to the vm, it works I've done it with the http server, now, with the tf2 server is a different story, it works on lan, can connect and everything, manage it through the screen command whenever I want to. sv_lan is set to 0.
Thing is it gives me this 127.0.1.1 internal IP, I really don't remember that happening when I did it on windows. The actual machine's ip is 192.168.88.220. So what is happening here? I don't know why I feel like "-ip" wouldn't do much for me but I might try it when I get home.
The the external IP is correct.
The VM is in bridged adapter mode so there should be no need to do anything else.
I have checked everything a lot of times so I don't really get it.
Now that I think of it it might be the screen thing, as 127.0.0.1 is the loopback IP maybe screen is running the server like a vm inside the vm it already is, but then again that would make no sense since I can connect to the server through 192.168.88.22. So if it's available internally why wouldn't it be from the outside if the ports are forwarded?
Welp.
Can you post a log?
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?
Can you post a log?
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?
yttriumCan you post a log?
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?
I'm gonna try that. VirtualBox. Thanks :D
[quote=yttrium]Can you post a log?
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?[/quote]
I'm gonna try that. VirtualBox. Thanks :D
Sounds to me like the VM has multiple network adapters and you need to force the server to bind to the non-default one by forcing the IP, like you suggested.
Screen does not act like a VM and would not cause this. I've used both Screen and Byobu with TF2 servers before without issue.
It's available internally because it's bindingto the internal adapter rather than the external one.
Are you using Virtualbox or VMWare?[/quote]
I'm gonna try that. VirtualBox. Thanks :D
You're forwarding port 27015 from the external IP to the 192.168.88.220 IP of the VM. However, your TF2 server is not listening on that address.
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow
You're forwarding port 27015 from the external IP to the 192.168.88.220 IP of the VM. However, your TF2 server is not listening on that address.
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow
ArieYou're forwarding port 27015 from the external IP to the 192.168.88.220 IP of the VM. However, your TF2 server is not listening on that address.
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow
:P thx
-ip actually, also, should I do like the actual IP? Or just the network one, to point to that specific adapter? I.e. 192.168.88.220 or just the network ip 192.168.88.0.
The electrecity went down right after I figured it out, I was Also halfway through setting up WOL.
[quote=Arie]You're forwarding port 27015 from the external IP to the 192.168.88.220 IP of the VM. However, your TF2 server is not listening on that address.
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow[/quote]
:P thx
-ip actually, also, should I do like the actual IP? Or just the network one, to point to that specific adapter? I.e. 192.168.88.220 or just the network ip 192.168.88.0.
The electrecity went down right after I figured it out, I was Also halfway through setting up WOL.
Adding -ip or +ip 192.168.88.220 (I keep forgetting which) will make your TF2 server listen on the right address.
edit: Oh I'm so slow[/quote]
:P thx
-ip actually, also, should I do like the actual IP? Or just the network one, to point to that specific adapter? I.e. 192.168.88.220 or just the network ip 192.168.88.0.
The electrecity went down right after I figured it out, I was Also halfway through setting up WOL.
Please
sign in through STEAM
to post a comment.