xxxxhnastyxxxx Posted May 13, 2015 Share Posted May 13, 2015 I understand that. Why do I get Beaver if all 12 players are in my geo filter? Link to comment Share on other sites More sharing options...
xxxxhnastyxxxx Posted May 13, 2015 Share Posted May 13, 2015 I have even added the Dedicated Servers and still get booted. Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Crossy Posted May 13, 2015 Netduma Staff Share Posted May 13, 2015 I have even added the Dedicated Servers and still get booted. You can't add dedicated servers to your allowed list. I'm not sure why your still getting booted - I'm not sure how destiny works but I'm sure Iain or someone will be around to tel you why Link to comment Share on other sites More sharing options...
xxxxhnastyxxxx Posted May 13, 2015 Share Posted May 13, 2015 I know that I just expand my geo filter over them. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 14, 2015 Administrators Share Posted May 14, 2015 Nasty I explained it fully in post above. The key is with strict mode on you can get the best quality games but it takes longer to find.With it off you won't get beaver but the qualty won't be as good, its still good just not as good. The reason you get booted is the dedicated server is blocked. Hope that makes sense, but please read the post above carefully. Thanks Link to comment Share on other sites More sharing options...
xxxxhnastyxxxx Posted May 14, 2015 Share Posted May 14, 2015 Can you give me a technical explanation of how the Netduma software blocks other players not in my geo filter? Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Crossy Posted May 14, 2015 Netduma Staff Share Posted May 14, 2015 Can you give me a technical explanation of how the Netduma software blocks other players not in my geo filter? There is a database which has all the IP's mapped out. If the Netduma sees an IP that is mapped outside of the GeoFilter then it blocks that IP from connecting. Probably more techy than that but that would be the basic principle Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 15, 2015 Administrators Share Posted May 15, 2015 Yes crossy is correct. Are you happy with that explanation mate? Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 15, 2015 Share Posted May 15, 2015 Has anyone been getting kicked to orbit in Destiny a lot more lately? Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 15, 2015 Administrators Share Posted May 15, 2015 Are you strict or non strict mate? Also what is orbit, sorry I don't actually play the game. Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Crossy Posted May 15, 2015 Netduma Staff Share Posted May 15, 2015 Are you strict or non strict mate? Also what is orbit, sorry I don't actually play the game. Orbit is kind of like the main menu in CoD Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 15, 2015 Share Posted May 15, 2015 Non strict. And I actually have my ping assist set to 75. Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 15, 2015 Administrators Share Posted May 15, 2015 oh right with non-strict there should be no issues. What version are you on? Also make sure you have bleeding edge cloud ticked! Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 15, 2015 Share Posted May 15, 2015 I'm on the newest firmware but I did not have the bleeding edge selected. I'm not at my computer right now but will do what you recommended and let you know if it happens again. Link to comment Share on other sites More sharing options...
caddy Posted May 15, 2015 Share Posted May 15, 2015 Has anyone been getting kicked to orbit in Destiny a lot more lately? Hey Nasssty, I don't have the Netduma yet, I've been waiting to hear about peoples' results with the Destiny upgrade before purchasing. However, I can tell you that even without the Netduma, I've been getting kicked to Orbit with alarming frequency for the past couple of weeks. The Bungie error code descriptions/fixes haven't helped. They say to power cycle the console, modem, and router. I do this, and I still end up getting kicked. I have a wired connection BTW, with 85mb down and 25mb up. And, no other games give me this issue. I've been getting mostly the canary error code, with a few marionberry error codes added for good measure. I think it happens more often when I am in a fireteam, rather than flying solo. I got booted 5 times in a row last night trying to complete the Weekly with my buddies. Then I played Crucible by myself, and did not get booted once. Iain, here's some explanations for a few of the Bungie error codes, so you can have an idea of what people are talking about when they mention beaver, canary, marionberry, etc error codes. They have a plethora of different names for their errors. ERROR CODE: CANARYIf you are seeing this error, it indicates a potential network problem with your console or network hardware. The first thing to do is to perform a cold reboot of your console and your networking hardware. To do this, follow these instructions: Exit Destiny and shut down your console. Once your console is fully shut down, unplug the power supply from the console for at least 30 seconds. Unplug the hardware in your networking setup and leave it unplugged for at least 30 seconds. Start to turn on your networking hardware, starting with the modem, and working your way out to additional hardware. Plug in and turn on your gaming console and launch Destiny. Attempt to reconnect and play Destiny. If power-cycling doesn't solve your problem, please perform further network troubleshooting by checking out bungie.net/networking for more information. ERROR CODE: MARIONBERRY If you are seeing this error, it indicates a problem with your networking setup. This can happen for a number of reasons, but often occurs after a WiFi blip, or when network or Parental Control settings have changed on your home network or game console. This error can show up when the router the console is connected through has gotten into a fundamentally bad state. Router reboots often help, but faulty firmware or failing hardware can lead to repeated occurrences of this error. To power cycle your modem or router please do the following: Log off of Destiny Turn off your PlayStation or Xbox console Power-cycle your networking hardware (router, modem, etc.) by turning each item off, then waiting 30 seconds before turning them back on one by one, beginning with your modem Once your home network is back up, turn on your PlayStation or Xbox console and relaunch Destiny Additionally, this error can also be caused by Parental Controls on some routers and may need to be adjusted to open up Player to Player connectivity. If you are encountering this error consistently, or if the above steps don't solve the problem, you will need to troubleshoot your networking setup to solve this issue, as port forwarding and firewall exceptions can help alleviate this error. For more information visit bungie.net/networking. ERROR CODE: BEAVER / FLATWORM / LEOPARD BEAVER/FLATWORM/LEOPARD errors are caused by a failure to connect your console to another player’s console via the internet. This can be caused by connection quality issues (such as packet loss, ISP saturation, or general Internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation. However, they are most commonly caused by router or network configuration issues. We are also actively investigating the possibility of bugs that are causing these errors to happen even for properly configured and well-functioning networks. We are actively investigating this family of errors, and the following conclusions may be useful to you: We tend to see these errors most commonly when multiple consoles are connecting to the internet through a single router. Some players have been able to work around this issue by enabling UPnP on their router. Strict NATs tend to see these errors far more often than Open or Moderate NATs – opening your NAT can significantly reduce the frequency of these errors. http://bungie.net/NAT Some types of connection quality issues (packet loss, etc) can trigger this family of errors. The quality troubleshooting steps described in http://bungie.net/NETWORKING can help. Configuring NAT, UPnP and port forwarding for Destiny Certain networking issues are related to having “strict” or “moderate” rather than “open” NAT. Please note that an open NAT isn’t a magic bullet that solves all networking issues. Changing the UPnP or port forwarding settings on your home network can potentially solve the following issues: Frequent BEAVER/FLATWORM/LEOPARD KTOs Unable to hear voice chat from other players in your own Fireteam Frequent empty towers Matchmade activities failing to find a game, resulting in ‘unable to find a match in time’/MONGOOSE errors If you aren't experiencing these specific problems, we strongly recommend that you don’t mess with port forwarding as it is a delicate procedure that may worsen your situation if done incorrectly. Before opening or forwarding ports manually, we would recommend making sure that UPnP is enabled on your router, as well as trying to connect your console more directly to your internet uplink to rule out other possible causes. What is UPnP?UPnP stands for Universal Plug and Play. It automatically handles port forwarding and other networking stuff many modern games need to work. Destiny users having problems can often benefit from enabling this if it's not on. Most routers should have it on by default. How do I turn on UPnP? The exact steps vary widely by router. Broadly you should follow these steps. Searching the internet for your exact router model's manual can be helpful. 1. Sign in with a computer to your routers admin page. 2. Look around "settings" and "advanced settings" type pages. 3. Try to locate UPnP. 4. If it's not enabled turn it on. You may have to reset the router. 5. Restart your console What is the difference between opening a port and forwarding a port? The first table lists notable ports to open (i.e. unblock) that can help Destiny perform better. If your router is blocking or slowing traffic on those port numbers, they need to be unblocked. The ports in the second table are ports that Destiny uses for inbound traffic that you might want to port-forward. Port forwarding is basically giving the router orders to forward incoming traffic on certain ports to a particular device within your network – it only affects incoming traffic, so all ports listed in the second table are inbound ports. Any port you might want to forward must also be open – there’s not much gain in trying to forward traffic that is being blocked! For example: I cannot log in to Xbox Live. After following all previous troubleshooting steps, if you are still unable to log in, check to see if you have a firewall that blocks all traffic on 3074. This means you will be unable to log into Xbox Live and 3074 needs to be unblocked in TCP inbound, UDP inbound, and UDP outbound. After unblocking 3074, you have the option of also port forwarding 3074 for TCP and UDP, if the guide above suggests that port forwarding would mitigate the issues you’re encountering. Port forwarding is not necessary for most people to play Destiny. Ports that should be unblocked to play the game: TCP outbound TCP inbound UDP outbound UDP inbound Xbox 360 7500-17899 30000-40399 53, 80, 3074 53, 88, 3074, 1001 53, 88, 3074, 1001 Xbox One 7500-17899 30000-40399 53, 80, 3074 53, 88, 500, 3074, 3544, 4500, 1200, 1001 53, 88, 500, 3074, 3544, 4500, 1200, 1001 PS3 7500-17899 30000-40399 80, 443, 3478, 3479, 3480, 5223, 8080 3478, 3479, 3658, 3074, 1001 3478, 3479, 3658, 3074, 1001 PS4 7500-17899 30000-40399 80, 443, 1935, 3478-3480 L3478, 3479, 3074, 2001 3478, 3479, 3074, 2001 Ports to forward to your console to provide open NAT: TCP UDP Xbox 360 53, 80, 3074 53, 88, 3074 Xbox One 53, 80, 3074 53, 88, 500, 3074, 3544, 4500 PS3 80, 443, 3478, 3479, 3480, 5223, 8080 3074, 3478, 3479, 3658 PS4 80, 443, 1935, 3478-3480 3074, 3478, 3479 Port forwarding can be an incomplete solution at best if you have more than one gaming console behind your router – you may fix the problem for one console, while causing more severe issues for the other. If you are afraid that you may have forwarded ports incorrectly, don’t worry: it can be undone. Please try removing any existing port forwarding rules that you implemented for gaming and enabling UPnP in your router settings if your networking hardware is updated to a recent firmware. UPnP is also typically the best solution if you have more than one gaming console on your network as each required port can only be forwarded to one console at a time. If you have UPnP on and no other forwarding rules and the problem still occurs, or if your networking hardware/setup doesn’t support UPnP, ONLY THEN attempt to forward ports manually. Please note: Not all NAT Type problems can be solved. If you are on a university or corporate network, or if your ISP limits what type of traffic you can send/receive you may have a NAT problem that is out of your control. If you have performed all of the troubleshooting steps called out above and are still hitting these errors, you may not be able to resolve this issue by changing your home network. Bungie is carefully monitoring BEAVER, FLATWORM, and LEOPARD issues preventing players from having a quality Destiny experience, and we are working very hard to investigate and address these issues. You can read about our ongoing progress below. Making this experience better for everybody is a top priority at Bungie. Recent updates on our investigations on BEAVER/FLATWORM/LEOPARD errors: Bungie is updating our recommended steps for those seeing these errors. Those experiencing BEAVER/FLATWORM/LEOPARD messages can potentially improve their Destiny experience with NAT or port forwarding adjustments. Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 15, 2015 Share Posted May 15, 2015 Yeah. I was getting the Beaver/Flatworm error code. Link to comment Share on other sites More sharing options...
Spartanogc Posted May 15, 2015 Share Posted May 15, 2015 I was getting kicked last night frequently Link to comment Share on other sites More sharing options...
PharmDawgg Posted May 15, 2015 Share Posted May 15, 2015 Maybe it's due to this new dlc they are getting ready to release. Link to comment Share on other sites More sharing options...
xxxxhnastyxxxx Posted May 15, 2015 Share Posted May 15, 2015 YES thats how I thought it worked. I was thinking maybe a patch to allow those dedicated servers to connect and not get blocked. Then again your geo filter wouldn't be geo filter with random dedicated servers just connecting. LOL thanks fells. I have just expanded my geo filter games are great. Link to comment Share on other sites More sharing options...
sncjez Posted May 16, 2015 Share Posted May 16, 2015 I noticed this for next weeks patch notes when HOW comes. Just a FYI Technical Added a new “Connection Recovery” System Specific player networking problems will now be fixed instead of kicking affected players to orbit This will be enabled first for Trials of Osiris and rolled out to other activities over time Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 16, 2015 Administrators Share Posted May 16, 2015 Hey guys I'm pretty sure at this point if you have "bleeding edge" and "Strict mode OFF" you won't get kicked and if you do I think it could be the game unfortunately. However as mentioned above if you have strict ON. You may get better games but you can get kicked so be prepared for it. With strict mode on make sure to keep the distance much larger. Thanks for all the info Caddy that is very kind of you. Cheers Jerry, is the setup still working well for you? Link to comment Share on other sites More sharing options...
gamerukali Posted May 24, 2015 Share Posted May 24, 2015 i was getting kicked last night only me constantly i had to turn geo filter off but even than i was getting kicked any solution ? like i say it was only me none of my friends Link to comment Share on other sites More sharing options...
Netduma Staff Netduma Crossy Posted May 24, 2015 Netduma Staff Share Posted May 24, 2015 i was getting kicked last night only me constantly i had to turn geo filter off but even than i was getting kicked any solution ? like i say it was only me none of my friends If the GeoFilter was off then the router is like any other router in terms of filtering (there isn't any). Could it have been an issue with your network where you were losing connectivity or something like that? Link to comment Share on other sites More sharing options...
Administrators Netduma Iain Posted May 25, 2015 Administrators Share Posted May 25, 2015 Hi GamerUkAli Crossy is correct if you have Geo-Filter disabled then its the game not the router. Maybe check if you have an open NAT when your Geo-Filter is off. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now