Page 1 of 1

[git-20120408] experimental server [offline]

PostPosted: Sun Apr 08, 2012 10:57
by mauvebic
69.90.180.65:30000

Image

mods:
flowers
moreblocks
star trek
growing trees: alien, bouleau (growth disable from time to time)

PostPosted: Sun Apr 08, 2012 11:13
by RabbiBob
What model do you have?

PostPosted: Sun Apr 08, 2012 11:18
by Jordach
i might know a way in.

PostPosted: Sun Apr 08, 2012 11:26
by mauvebic
its a "G Wireless Router version 3000" F5D7234-4

PostPosted: Sun Apr 08, 2012 11:53
by RabbiBob
http://www.belkin.com/support/article/?lid=en&pid=F5D7234-4&aid=14397&scid=0

Page 63 - Firewall->Virtual Servers

  • Log into your router
  • Open the virtual servers section under Firewall
  • Click enable
  • Put a name (Minetest) in Description
  • Put the inbound port as the one your server is running (30000 by default)
  • Type: UDP
  • Add the internal IP of the computer running the server
  • Put the private port as the one your server is running (30000 by default)
    • Apparently you can have a different port on your external connection than your server port, but let's not confuse things.
  • Apply Changes

You will need to make sure that any firewall on the computer hosting the world also allows port 30000 to pass through, else it will fail. After you've done all of the above, start the server and have someone connect to your internet address.

If that doesn't work, the Remobo/Hamachi VPN users will post instructions on how to do it that way. Good luck.

I can't believe they have Active Worlds as the drop down example in the manual above. That hit major popularity back in 1997 as a community based virtual reality building game (this was Second Life before there was Second Life) and here we are 15 years later still playing with blocks.... ;-)

PostPosted: Sun Apr 08, 2012 11:56
by Calinou
Edited your post - Minetest uses UDP, not TCP. This is very important, you need to set the correct one.

PostPosted: Sun Apr 08, 2012 12:03
by RabbiBob
Calinou wrote:Edited your post - Minetest uses UDP, not TCP. This is very important, you need to set the correct one.


Thank you Calinou. I wasn't entirely sure about that and unable to test on the current machine.

PostPosted: Sun Apr 08, 2012 14:01
by mauvebic
Thanks! sorry for the delay, was modding and distracted, ill give that a shot now and share an IP via PM see if someone can join me

PostPosted: Sun Apr 08, 2012 14:04
by Jordach
I c an try to join, version please?

PostPosted: Sun Apr 08, 2012 14:08
by mauvebic
RabbiBob wrote:
I can't believe they have Active Worlds as the drop down example in the manual above. That hit major popularity back in 1997 as a community based virtual reality building game (this was Second Life before there was Second Life) and here we are 15 years later still playing with blocks.... ;-)


I *found* minetest looking for a linux port of activeworlds lol

PostPosted: Sun Apr 08, 2012 14:12
by Jordach
Really just email me here jordach.snelling@gmail.com

PostPosted: Sun Apr 08, 2012 14:13
by mauvebic
107.6.56.215:30000

PostPosted: Sun Apr 08, 2012 14:16
by Jordach
Minetest keeps on going, Connecting to Server..

PostPosted: Sun Apr 08, 2012 14:24
by Jordach
Mt wont connect. IP is real.

Image

PostPosted: Sun Apr 08, 2012 14:27
by mauvebic
Thats damn peculiar. Must be something about arch linux. Port forwarding seems to work though :S

PostPosted: Sun Apr 08, 2012 14:28
by RabbiBob
Go here (where the end of the IP is your open port) and it will tell you if your port is open.

https://www.grc.com/x/portprobe=30000

PostPosted: Sun Apr 08, 2012 14:29
by RabbiBob
mauvebic wrote:Thats damn peculiar. Must be something about arch linux. Port forwarding seems to work though :S


Do you have a firewall running on the distro itself?

PostPosted: Sun Apr 08, 2012 14:29
by mauvebic
it gave me:
Stealth Unknown Protocol for this port
Unknown Application for this port

i didn't install any firewalls on arch

PostPosted: Sun Apr 08, 2012 14:34
by mauvebic
Do iptables have something to do w/ it? im on protocol 9 btw

PostPosted: Sun Apr 08, 2012 14:47
by RabbiBob
Stealth = port isn't open all the way through.

Iptables is a firewall and is probably what needs to be set up to allow the port through to the server:

https://wiki.archlinux.org/index.php/Iptables

Seems like you are close, just the last hurdle.

PostPosted: Sun Apr 08, 2012 15:03
by mauvebic
i went into /etc/sysctl.conf and put:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
Code: Select all
net.ipv4.ip_forward=1
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding=1


and i added iptables to daemons. But i still get "Stealth" :-S

I have to do a quick run to the grocery store, ill check back in 40 minutes and give it another shot :-)

PostPosted: Sun Apr 08, 2012 16:13
by mauvebic
i disable the modem's firewall and now i get "Closed" for that port. ive set the modem to portforward to the w/less network


heres what the settings look like:
Image

PostPosted: Sun Apr 08, 2012 16:35
by mauvebic
When i setup DMZ on the router it gives me 'Public IP 192.168.1.5 -> private IP 192.168.2.2'
I have a feeling my computers default route should be 192.168.1.5

PostPosted: Sun Apr 08, 2012 16:36
by RabbiBob
Private IP address s/b the server's internal address. I believe that is 192.168.1.5 in your example.

PostPosted: Sun Apr 08, 2012 17:09
by Jordach
Go here to get your "public" IP: whatismyip.com

Then, using the IP in big letters. Post it here so we can test, also, give Minetest version numbers, so we can connect to you, without client guessing.

PostPosted: Sun Apr 08, 2012 17:32
by RabbiBob
Family is over for Easter Dinner. Will get back to you later.

Basically you've got to pass the port from the router and point it right at the IP of the server.

For example, my router is 172.25.4.1 and my server is 172.25.4.150 on my internal network. I have to tell the router to pass all port 3000 UDP traffic from the Internet to 172.25.4.150 (and then make sure the server at 172.25.4.150 isn't blocking that port as well).

PostPosted: Sun Apr 08, 2012 17:36
by mauvebic
allright, with the wilan in access point mode, everything is on the same network (at least) :-)

router:192.168.1.4
modem: 192.168.1.254
me: 192.168.1.2

PostPosted: Sun Apr 08, 2012 22:15
by RabbiBob
-----
Another test to know if it's your iptables or your router requires another computer on your internal network: try to connect to the server at 192.168.2.2 Port 30000. If it fails, then it's your server and most likely the firewall.

----

Random thought: Did you restart your iptables after the changes and you still can't connect?

/etc/rc.d/init.d/iptables restart

If so.....

--------------------------

We may be convoluting things.

Your screenshot shows "192.168.2.x" as being the available IP range from your router's config page. You said above that your IP is "192.168.1.2", but I suspect it is "192.168.2.2". To clear this up, get the IP of your server. Arch linux should spit it out with the following command:

>ip a


Image

If you have a typical home setup, you'll have a cable or dsl wire that goes into a cable or dsl modem. From there, you most likely have a router connected to the modem via an Ethernet cable. From there, your computer is connected to the router by another Ethernet cable (or wi-fi).

You usually do not make changes to the modem. It just runs and does its job. It usually has its own IP address that is 1) an internal IP address and 2) different than your router's IP address.

Your router may or may not see the modem's IP (yours may be seeing it from what I'm reading), but we shouldn't really care about it. Your screenshot looks like you've done this properly. If TCP\UDP is an option, you can set that as well and cover both types (Calinou says it is UDP, so we'll can take that as truth or set the value to cover it all).

Regardless, now your router is set to pass port traffic destined for port 30000 onward to 192.168.2.2. If your router has logging, you actually should see requests go through if people are trying to connect from the internet (you'll have to work with someone actively to see if they generate traffic).

So we'll assume that port 30000 is making it through. If iptables is on, you'll need to let it pass through. I have little experience with this specifically and could only suggest googling "ip tables port forwarding". The premise is exactly the same as what you did to the router: allow port 30000 to pass through the firewall.

If you get this set up and the server is running, it'll accept a connection.

That's about as much blind help I can give, I hope it helps out.

PostPosted: Mon Apr 09, 2012 03:50
by mauvebic
Ive tried everything:
router port forwarding (fail), then set it as access point which meant the router and all hosts were on the modem's network.
then i setup port forwarding on the modem (fail). Then i enable IP passthrough so my host would have the public IP (fail). Both the routers' and the modems' firewalls were disable.

I think this is an Arch issue. VLC remote and VLC web interface haven't worked in three weeks either, something about socket permissions being denied. I filed a bug on that so ill check it out.

Thanks anyways :-) ill post back if/when i get it to work :-)

PostPosted: Thu Apr 12, 2012 20:17
by mauvebic
I was able to connect to my server using a laptop, i think it should work now :-)