46
Help / Re: Help me set up my blockland server (port bullstuff)
« on: July 05, 2015, 02:09:25 AM »
after a really long chat and debugging we've resolved several issues that swollow was having
now, it's been boiled down to one final issue
first of, swollow's etwork topography consists of a stuffty westell DSL/ethernet converter router (192.168.1.1) his family probably got from his stuffty no-name telecom, which is the first thing between the network and the internet.
after that is a dlink router at 192.168.1.47, which is running the wifi network everything is connected to. after that is swollow's computer at 192.168.1.51, as you can see above.
after quite a stuffload of difficulty, the westell router is configured for upnp as well as the dlink one. blockland runs under upnp, and you can join the server... but then you promptly get an authentication check failure, because everyone who joins the server is given the ip of 192.168.1.47
this is not an issue with port forwarding, this is an issue with swollow's bizarre network topology and stuffty routers
does anyone have any idea how to make the dlink router function not like a transparent proxy?
now, it's been boiled down to one final issue
first of, swollow's etwork topography consists of a stuffty westell DSL/ethernet converter router (192.168.1.1) his family probably got from his stuffty no-name telecom, which is the first thing between the network and the internet.
after that is a dlink router at 192.168.1.47, which is running the wifi network everything is connected to. after that is swollow's computer at 192.168.1.51, as you can see above.
after quite a stuffload of difficulty, the westell router is configured for upnp as well as the dlink one. blockland runs under upnp, and you can join the server... but then you promptly get an authentication check failure, because everyone who joins the server is given the ip of 192.168.1.47
this is not an issue with port forwarding, this is an issue with swollow's bizarre network topology and stuffty routers
does anyone have any idea how to make the dlink router function not like a transparent proxy?