Raelus
-
Posts
74 -
Joined
-
Last visited
Posts posted by Raelus
-
-
ah, you're right.
as good as linksys hardware is. (about the best you're going to find for commodity hardware routers)
it's software does leave a bit to be desired.
i build my own routers so... i haven't actually touched commodity routers in quite awhile. (except to remove them) :P
pfSense is my personal favorite as of late.
same S#&$ here i log in all system nominal log out log in again strict nat port forward doesnt help firewall disabled doesnt work viruscanner disabled geus wot doesnt work. this is not a problem on our side its them they screwing us over with there servers they use. me and me m8 played i think a few matches together by just a gues being lucky that the servers let us trough. all other games i play we can join up use in game voice chat etc etc etc we even tried logmein hamachi or some S#&$ that we creat a private network just for us two but geus wot happend IT DIDNT WORK
Curious, but what's the router model and approximately how large are your clan and friend lists?
Working initially and not working shortly after leads me to believe a router issue and there's a potential problem related to large friend lists that fits this behavior.
EDIT: Also, do you have more than one computer running Warframe in your home?
-
looking at his supplied information a bit more. his router is supplying the same range of IP's as it's receiving. (192.168.1.X)
and doesn't offer the ability to change it.
192.168.1.10 is the router's IP on the LAN interface (his pdf link, page 3). You can also confirm this by noting that the DHCP server lease range skips 192.168.1.10.
The WAN interface is set to DHCP. We can't see the IP it's getting unless he posts the router's status page; the configuration page isn't showing the leased IP.
-
The router has a private IP and is already shielded from the open internet, you're correct. I was thinking about exposure to all other users on the apartment's private network (the guy next door, etc).
And yes, I forgot to mention disabling the DHCP server if he's going to use it as an access point as opposed to a router. Setting a static IP in the lease range shouldn't break it though as long as the IP chosen isn't currently in use. Any properly configured DHCP server tests an IP before leasing it in case someone is squatting on it (though yes, it is improper and a potential problem). All of his other devices would receive IPs from the apartment's upstream DHCP server; it's just the router that would need to be statically set due to GUI restrictions. Ideally flash it with 3rd party firmware where it can be configured to be a DHCP client on something other than the WAN interface but this can be difficult for a novice and outside the support scope I can assist with.
Long term, you're right. Replace it in this scenario.
-
try connecting your pc directly into your wall jack. this should lead to your apartment complex's router. which in turn leads to your apartment complex's modem.
depending on the settings for it (hopefully it has upnp enabled) this might work for you without the need for anything else.
if it does, you should be able to change your router out for a switch (if you have need for more devices to be plugged in)
this won't help you in the arena of wifi, but for testing purposes you can see if you can at least get up and running.
if not, follow the advice of Raelus and see if whomever handles the apartment complex's IT can help you get things configured / forwarded.
This was a suggestion I was reluctant to make because, depending on the complexity of the apartment network, he may expose his computer, printers, shared files, etc, to all other users on the apartment network whereas his router prevented that leak.
To expand on Xethier's solution, if you do find that it works by plugging in your PC straight to the apartment network without the router you can use the router as a switch by not connecting a wire to the WAN port; just plug the apartment network into one of the four switch ports. This will allow you to still use multiple devices and wifi without buying more stuff. However, you'll need to set a static IP on the router for this to work.
I discourage this solution due to the potential privacy implications but it's your decision to make. -
I guess i am boned. Its an apartment and they are given service from suddenlink. I guess ill just wait till i move. maybe i might still want to play then
Ah hah! An apartment network. Shared among all tenants I am guessing?
Odds are, your landlord (or building manager) has access to the modem. If you're on good terms with him/her, you can politely ask them to forward the Warframe ports to your router. You can then use your router to forward those same ports to your PC.
Your other options include subscribing to a VPN service (not free) to tunnel out and get access to a public IP or getting service from a source other than what's provided to the apartment by default.
Otherwise, no amount of button pressing or configuration is going to fix it for you. Sorry.
-
No I dont have a separate modem. I just the Ethernet cable to router then plug another Ethernet cable from the router to pc
So, the router has a cable to the computer and a cable to the...? No other box, you're wired with ethernet straight into the wall?
Is this a university or corporate network? You're boned in those cases as any IT department worth its salt won't allow upnp or port forwards.
EDIT: You previously said your ISP is suddenlink which appears to be a cable internet provider. You should have a piece of equipment on the premises that has plugs for both ethernet and a coaxial cable. That would be the modem.
-
Prease, I beg you, help me!
Cisco Linksys E1200
ISP: Suddenlink
Router Settings:
http://www.scribd.com/doc/181830724/router-settings-pdf
Ive done all combinations of turning on/off uPnP
This really blows. Maybe recruit someone who knows how to deal with these sort of issues?
The E1200 is a router only model, so I'm assuming you have a modem as well. Further, the E1200 is getting its IP by DHCP from the modem so I'm assuming a double-NAT scenario.
You need to forward the ports in the modem as well.
-
It's very likely a desync issue (eg. the client and server don't have in-sync information about the game state). There's been more and more "trust" appearing in the client than before as I'm able to loot mods during bad lag whereas I couldn't months ago. Now it's limited most notably to energy and ammo that stop getting recognized during bad lag as if it's waiting for host confirmation given these items affect game state. This is guesswork, however.
Interestingly though, I have seen more bandwidth being used by Warframe as patches progress. During the survival event I was topping out near 1Mbps upstream and now during the Gradivus event I was topping out at 1.3Mbps upstream while hosting. I suspect the increasing demand is stressing some people's connections where there wasn't a profound issue before.
-
IT WORKED!! I switched the two routers, everything was screwing up then my Dad managed to get it connected back to the internet, then, before even using port forwarding, me and my bro ran the game and we could finally see each other online in the contacts list. Only one small issue now, it seems my brother can join my session, but I can't join his, not too big of a problem but slightly weird.
Fantastic! Glad to see that you got a solution that worked and didn't even have to shell out more money to do it!
-
Ok, a few more things I've found out. One, I am on a two router network but the first router is only acting as a switch and shouldn't be doing anything to cause me problems. Two, the router that is my gateway is a Linksys WRT54G v4. The model of my switch router however, is a Netgear N300(or WNR2000 v2), which I'm positive is a newer router and I have been considering switching the two around so that the newer one can act as the gateway.
@Raelus it does appear that both of my routers support NAT loopback, although were I got the info from didn't mention the version of the WRT54G and as I recall there are like 9 or 10 different versions.
@MachFarcon Yes, as mentioned above I think I'll try switching them around, possibly tonight and see if I have time to post if its working any differently.
Ahh yes, the WRT54G. I love that model but it kind of went to crap after v2. It's spiritual successor was really the WRT54GL beyond that point. As for its loopback capabilities, I have no idea which revisions support it and which don't. Results are mixed and I can't find a resource that breaks it down by hardware revision or firmware.
The WNR2000, however, is listed http://opensimulator.org/wiki/NAT_Loopback_Routers'>here as supporting NAT loopback as of firmware rev. 1.2.3.7. Since you have that router on hand, I'd suggest swapping the two and seeing if you get better results. Remember to forward your ports with the WNR2000. Also note that if your firmware is prior to 1.2.3.7 then you'll need to update it.
-
Game telling me that I have a Strict NAT. It never occurred to me that I should have forwarded my other modem. Anyway, just changed it and I finally got rid of the message. Thanks alot man. Means alot to me. :)
Glad it worked!
-
Thank you both :) Though I'm getting a Strict NAT problem even if those two are forwarded think you guys can help me alittle more?
By "Strict NAT problem," do you mean the game is telling you that you have a Strict NAT? Or are you inferring this from some other behavior?
Also, this appears to be a standalone router. Do you have a separate modem provided by your ISP? If you do and if it's configured in routing mode then you may need to forward ports there as well.
-
Regarding you being able to join a game with your bro when neither of you is host seems to be in line with the "single IP address" issue i.e. your shared internet connection/router/proxy IP
It's something to investigate on the Network Layer configuartion level (i.e. IPs, subnets, proxy rules, ports etc etc), and not necessarily the hardware(wires/routers) level
Network Address Translation ("NAT") exists to solve the single IP address problem and it is controlled entirely by the routing device.
Manufacturer's implementations of NAT, however, vary and often don't follow standards completely. Many routers also have insufficient memory to track hundreds or thousands of active states and the NAT table can become full causing all kinds of weird connection issues.
Having two internet connections would technically work, but it side steps the issue. Its like replacing the whole car because you got a flat tire. Very excessive.
-
Your forwards appear correct.
Also, ports 80 and 443 are not required by Warframe and shouldn't be forwarded unless you're running a web server.
no, type should be UDP not both
Both means TCP and UDP which includes UDP. Forwarding both protocols is not wrong.
-
What I just mentioned about being able to play together like this leads me to ask, is this a problem on my end, or a problem with the way warframe handles connections?
It's partially both. Warframe has a lot of holes in its netcode from what I've seen and doesn't account well for routers that don't follow standards thoroughly. This leads to a lot of very mixed results in connectivity and particularly affects people with bargain quality routers.
The second thing, although much smaller and probably means nothing anyhow, is that when either of us hits the contacts button, we appear offline to each other on the friends tab and the clan tab. However, in the chat box, if I switch to clan chat(we are both in the same clan), we both appear online and we can chat with each other.
The game handles chat completely differently from the way it handles contact lists so it helps not to think of them as the same.
Chat is handled by a central server. Everyone connects to the chat server and receives chat participants from the server.
The friends list is entirely P2P. On sign-in, your client begins attempting to make direct connection to everyone on the friends list using IPs supplied by DE. Connections that fail (because they're offline, behind a NAT, or other issues) the player appears offline to you.
The fact that you cannot directly connect to the other PC in your house yet you can see each other in chat is consistent with this behavior.
Fun fact: I had an old router that would completely crash every time I loaded the list of running game servers in Steam. Opening hundreds (or thousands) of connections at once to query server status would overrun the routers internal memory while tracking all those states. I think DE has recently discovered that the same is possible for people with very large friend/clan lists when the game starts querying those lists on login.
@Raelus I have no clue if our router doesn't support that, on the web setup page it mentions nothing of that and I'd have to do some digging around to find the manual, although I may just have to search up my router online
NAT Loopback is by no means a new thing but if the router is a low end unit it may not support it or may not be properly implemented. Care to share the router model?
After doing some more research our network has two, or possibly three routers in our setup, I'm not quite sure how it all connects up because it was our Dad that set all of it up and to me it's just a mass of a bunch of wires. I'll have to ask him about it some more although he originally was the one who told me how to port forward it but I'm not even sure if that works and Warframe is just being derpy, or if the port forwarding didn't work at all. I just really wished it would work. I'll get back to you people once I do some more research on this.
I wouldn't worry about port forwarding being an issue. If either of you can play online either independently or simultaneously, can host games for others, and don't receive errors about NAT for firewalls then you are configured properly and the port forwards are functioning.
Also, the part where the two of your computers can play together only when someone else hosts and invites you two is consistent with the NAT loopback thing. In this scenario, your computers aren't talking to each other directly but instead by way of this other host which is why it works without being able to directly talk to each other.
Hope some of this is useful to you. I'm a network tech and I know my way around at least the basic stuff so feel free to drop other questions relating to the game connectivity.
-
If you are running on different ports, both of you can play normally online (no errors about NAT, firewall, etc), but still cannot see or connect to each other, then it's possible your router doesn't support whats called https://en.wikipedia.org/wiki/NAT_reflection#NAT_loopback'>NAT Loopback and you may need to replace it. Before doing so, check the manual for any options to enable NAT loopback and consider updating the firmare if it is out of date.
-
No. That is the whole point of UPnP.
Sometimes I still get Strict NAT error when everything is actually fine.
In some cases, it's acceptable that they do not match. Warframe is not one of those cases and it breaks if the port pairs don't match.
Going by OPs photo, Warframe is running on three PCs (or has ports forwarded to 3 IPs in the upnp table, possibly due to DHCP changes) but all three are running on the same ports. Since upnp appears to be working, changing the ports used in the in-game menu and restarting ought to fix it.
As to your assertion that mismatching ports are OK for Warframe, here is why that is incorrect:
When warframe conducts a NAT test, it sends out a test packet saying what port it is using. Normally, this is sent from the same source port that the game is advertising it is running on. In a direct connection or proper NAT, the game sends a packet from 3962 saying "HI! I'm using port 3962."
When the router is rewriting the port, as in this case, the game is sending a packet from 3962 on the local PC, but the router changes the packet source port to something else, like 3964 but the content of the packet still says "HI! I'm using port 3962." The Warframe matchmaking servers don't catch this inconsistency and respond on 3962, the port the packet is advertising and not the origination port on the router. The response comes back on a port the router is either configured to send to another PC or is not configured for at all; thus you then get a NAT error. It's also possible that it is catching the inconsistency and throwing a NAT misconfiguration error. The ports are expected to be the same.
If Warframe paid attention to the source port on the packet and responded on 3964 like the router is advertising then yes the upnp rewriting would work as you say. But it doesn't and it's doing something else instead.
Source: I'm a certified networking tech and I do this stuff all the time. My example may not have the exact port instructions the game uses, as I don't have access to the networking code, but the general principle should be clear enough.
EDIT: The client/server interaction might be more complex than my example but suffice to say I've seen it not work whenever port rewrites are at play.
-
So, here we go. I love this game, I play it a little bit ( steam says I've got 225 hours. Needs moar.) But suddenly the Strict NAT has arisen.
Okay fine. Go back into my router and check the port forwarding, Nope, shes all good still.
The only recent change was my brother moving out and thus not needing to port forward his pc for teamplay.
But whats weird, is that this started some three week AFTER he moved out, and we had been playing since then.
And now I am stuck is with this lovely Strict NAT that will not go away.
I have since tried changing the ports the game asks for and port forwarding them,
Disabling UPnP on both the router and the game itself.
Even updated the router firmware.
All to no solution.
Honestly, I love this game. the longer I watch it the better the game gets.
I loved it enough to put my money into it to the tune of 270$ for the top tier founders pack.
I would really like to play the game, but I must say that it gets extremely old to play solo. Very quickly.
1) Make sure you're forwarding ports to the correct IP. If the devices in your network have changed and your router is using DHCP then your private IP may have changed. Check the IP Warframe is telling you to forward to against the IP you have configured in the router.
2) If you're manually forwarding ports, disable upnp and leave it off. Also clear the upnp table in the router.
3) Restart all of the networking equipment. This includes both the router and any ISP provided modem.
If Strict NAT is a new issue, it's due to a change in your equipment or the sheer need to restart something. If none of these help, post back with a screenshot of the Warframe error and your router's port forward configuration page and upnp table (if that's still enabled). Either myself or someone else with a networking background can probably help given the right information.
-
So uh.
The picture pretty much explains itself. The ports are open and UPnP is enabled and I still have the issue.
Your internal and external forwarded ports do not match on the highlighted lines.
They have to match. -
Stopping by to confirm this is an issue, and repeatable at that.
1) Queue for a mission
2) Abort the queue. This takes you back to the planetary overview now.
3) Select any planet and get error messages:
* "Could not join. The game session is no longer available."
* "Failed to create session. Please try again."
Requires a client restart to fix.
So every time you abort out of a queue, you have to restart the client. Fun.
-
Known issue and there's even a post about it on the first page, fifth thread down at the time of this writing.
https://forums.warframe.com/index.php?/topic/102333-corpus-infested-mission-io-bug-invisible-floor/
-
Why didnt you jump in?
Of course I jumped! The view was less impressive, though,
-
Had a very lagged game and ended up being left behind at extraction!
UI completely disappeared, mob AI shut off, and couldn't abort mission either as the mission was completed. Ended up force quitting to get out of this.
Also, watch out for that last step - it's a big fall! Nice artwork though.
-
Checking in that the issue started for me as well after the latest hotfix just after 5PM.
Launcher cannot connect to the update servers.
0.155 Sys [Info]: Cache Host: content.warframe.com [205.185.216.10]0.160 Sys [Info]: Origin Host: origin.warframe.com [96.47.186.235]0.161 Sys [Info]: Downloading cache manifest index...[SNIP]0.442 Sys [Info]: /Packages.bin is out of date; fetching updated version from share...30.959 Sys [Error]: HttpSendRequest failed to content.warframe.com: ERROR_INTERNET_TIMEOUT61.489 Sys [Error]: HttpSendRequest failed to content.warframe.com: ERROR_INTERNET_TIMEOUT92.007 Sys [Error]: HttpSendRequest failed to content.warframe.com: ERROR_INTERNET_TIMEOUT122.609 Sys [Error]: HttpSendRequest failed to content.warframe.com: ERROR_INTERNET_TIMEOUT122.609 Sys [Error]: /Packages.bin is missing from cache share
Despite the failures, I can make a connection just fine. Something broke after patch.>tracert -d content.warframe.com Tracing route to cds.b5q9z7i8.hwcdn.net [205.185.216.10]over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms xxxx 2 <1 ms <1 ms <1 ms xxxx 3 9 ms 9 ms 11 ms xxxx 4 9 ms 19 ms 9 ms xxxx 5 38 ms 10 ms 13 ms 216.55.44.17 6 20 ms 23 ms 24 ms 216.156.0.153 7 18 ms 16 ms 15 ms 207.88.14.226 8 32 ms 22 ms 15 ms 216.156.84.106 9 17 ms 23 ms 15 ms 209.197.6.10 10 15 ms 15 ms 15 ms 205.185.216.10 Trace complete.
EDIT:
Easy fix actually, I dumped the cache files in the Windows account profile.
Deleted C:\Users\USER\AppData\Local\Warframe and the game launched just fine.
Love that cache corruption.
Catch-22 Dns Lookup Failed Problem
in Multiplayer
Posted
DNS lookups have nothing to do with a dynamic or static IP. If you're having DNS issues, it's usually one of two main causes.
1) You have enough malware to sink a ship. DNS hijacking is a common tactic by malware and it will mess with all sorts of things.
2) Your DNS settings are poorly configured or your provider just sucks. Try using Google's open DNS to rule this out.