Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
if you connect to your tp link router click on DHCP then Address Reservation and give your pc an specific ip ( this will make sure that your pc will always gets this internal ip ) like 192.168.1.130 / 192.168.0.130 ( depends x.x.0/1.x < depends on your network setup ) after you have an ip set you can forward the port to that ip.
if you friend will connect to you over the internet he would need your internet ip
http://whatismyipaddress.com/de/meine-ip
and then he needs to add the port at connection x.x.x.x:34197
Do not deactivate the windows firewall but if you have another antivirus with firewall just deactivate it for testing purposes so you can be sure that the firewall does not block the port
A side question - Why on earth do you have TWO functioning routers? You really, REALLY need to set either of those in Bridge mode, so it only functions as a switch. Otherwise you're asking to have the worst possible experience trying to host anything.
Give your buddy the internet IP, not the IPV4.
So you have one router that's nice to use... so what about the other one? I don't see why you wouldn't want to bridge that to be honest. You're just asking for all manner of packet trouble by having two devices trying to fight for your local network ownership.
Erm... Nail... IPv4 has nothing to do with whether or not you're using a local IP or one on the internet. In fact IPV4 has been the standard for as long as the internet has been around (more or less)
You may be thinking of local IPs which tend to be in the 10.0.0.x or 192.168.x.x range - But those are IP(v4) addresses too. An IPv6 address looks something like this: FE80:0000:0000:0000:0202:B3FF:FE1E:8329
IPv6 addresses aren't really taking off as fast as the industry would want - even though we have technically run out of IPv4 addresses.
Edit: But yeah - You definitely need to give the friend your public IP, not one of your local ones. That'd be liked asking the mailman to deliver across country by handing them the door number, not their postal code.
Yeah, I was simply using the convention that IPCONFIG uses for an IP on your local network behind a router. I should have been more clear about not using the local IP. I think my point was taken though.
Maybe.
Heck. I don't know.
question is, are they behind or parallel to each other?
http://images.akamai.steamusercontent.com/ugc/308866715004854556/65BAD1963F91975053A299CB30236CBDF82CAD33/
figure left, the modem-router from your provider is the yellow divider, your tp-link one is the red one, connectet to the first via "internet"-port on the tp-link
figure right, modem-router is the real router and the tp-link is connected via normal ethernet-port on the tp-link, tp-link is nothing more than wlan-ap, modem-router does dns, dhcp and gateway
Make sure that your modem LAN side IP(s) is a different range to your Router LAN side IP(s).
For instance the Modem LAN side could be 192.168.0.# range, while your Router LAN could be 192.168.1.# range.
(The reason for making the ranges different is that some Routers/Firewall block data being sent from IP's within the same range as the LAN and this can cause problems when configuring servers.)
I run
[ISP box bridged]->[router/NAT]->192.168.1.0->[router]->10.5.2.0->[router]->172.17.2.0 and i just set portforwarding in the first router even for the 172.17.2.0 subnet. The rest is handled by static routes in the routers.
youll just have to make sure everyone who is playing has the client and is registerd on it, then if you used evolve you make a party and invite your friends into it and it'll auto assign local network IPs, you just right click and copy the IP or hand jam it then put that in Factorio, don't even need the port #, and voila you'll be playing as if all the ports were forwarded or you are all on the same network... minus all the route-around you are trying to do here... You can use such clients for other games too, like risk of rain etc.