Netduma Alex Posted July 30, 2019 Share Posted July 30, 2019 The firmware's going through final testing right now, so unless any major issues are found... Link to comment Share on other sites More sharing options...
Odin Posted July 30, 2019 Author Share Posted July 30, 2019 1 hour ago, Netduma Alex said: The firmware's going through final testing right now, so unless any major issues are found... So roughly when? Also is the issue that we are reporting going to be looked at? Surely VLAN tagging should only be used on the WAN side not also the LAN? Link to comment Share on other sites More sharing options...
Netduma Alex Posted July 30, 2019 Share Posted July 30, 2019 I can't say when, it's up to NETGEAR to decide when they release it. And yes we're going to look at this issue, although I have a feeling it's caused by netgear's part of the software. Link to comment Share on other sites More sharing options...
Odin Posted July 30, 2019 Author Share Posted July 30, 2019 11 minutes ago, Netduma Alex said: I can't say when, it's up to NETGEAR to decide when they release it. And yes we're going to look at this issue, although I have a feeling it's caused by netgear's part of the software. Thanks. So if it is a Netgear issue are you going to take it up with them or do we need to? They fixed this poor bug in other routers. Hardly fitting for one of there flagship routers to have such a silly floor. It is not only an issue with NAS' but also IP cameras etc.... Cheers. Link to comment Share on other sites More sharing options...
Netduma Alex Posted July 30, 2019 Share Posted July 30, 2019 I agree, but NETGEAR are certainly aware of this problem. Link to comment Share on other sites More sharing options...
JoshGre Posted July 31, 2019 Share Posted July 31, 2019 Well, it turns out I've managed to fix it, in a round about kind of way. I'm using a DM200 Modem with the XR500. If you want the DM200 to handle the VLAN settings, instead of the XR500, you have to set them up when the modem is in Modem/Router mode and then change it to modem only and do not allow VLAN passthrough. After hours of frustration, I'm just glad I've managed to figure this out. Odin and Netduma Fraser 2 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted July 31, 2019 Administrators Share Posted July 31, 2019 20 minutes ago, JoshGre said: Well, it turns out I've managed to fix it, in a round about kind of way. I'm using a DM200 Modem with the XR500. If you want the DM200 to handle the VLAN settings, instead of the XR500, you have to set them up when the modem is in Modem/Router mode and then change it to modem only and do not allow VLAN passthrough. After hours of frustration, I'm just glad I've managed to figure this out. Great to hear that, thanks for posting a solution! Link to comment Share on other sites More sharing options...
Odin Posted August 1, 2019 Author Share Posted August 1, 2019 I can confirm that the above solution also works for me. Crazy but it does work. Basically do not let the XR500 handle any of the VLAN stuff for you and amazingly all works fine. Thank you JoshGre, you saved me buying a switch. This stupid issue has already forced me to buy other NAS, so now I have two 😞 Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 1, 2019 Administrators Share Posted August 1, 2019 15 hours ago, Odin said: I can confirm that the above solution also works for me. Crazy but it does work. Basically do not let the XR500 handle any of the VLAN stuff for you and amazingly all works fine. Thank you JoshGre, you saved me buying a switch. This stupid issue has already forced me to buy other NAS, so now I have two 😞 Great to hear that, hopefully we can get this resolved shortly in an update Link to comment Share on other sites More sharing options...
JoshGre Posted August 1, 2019 Share Posted August 1, 2019 Just now, Netduma Fraser said: Great to hear that, hopefully we can get this resolved shortly in an update Fraser, From what I understand from the research I did, the problems arise because there is no option to on the router to use a VLAN ID on just the WAN traffic, what's happening is there is some issue when using VLAN with the options you have on the router where it will tag all traffic, which means even LAN traffic is VLAN tagged which is causing a routing issue. The best way I can think to resolve it is to be able to tag the 'internet' port as you call it on the device manager and then all will be fine. Thanks Josh Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted August 1, 2019 Administrators Share Posted August 1, 2019 5 minutes ago, JoshGre said: Fraser, From what I understand from the research I did, the problems arise because there is no option to on the router to use a VLAN ID on just the WAN traffic, what's happening is there is some issue when using VLAN with the options you have on the router where it will tag all traffic, which means even LAN traffic is VLAN tagged which is causing a routing issue. The best way I can think to resolve it is to be able to tag the 'internet' port as you call it on the device manager and then all will be fine. Thanks Josh I think you're right as when I tested it myself I found that to be the case so I think when that is done its just a case of double checking/fixing QoS with that and it should be fine. Link to comment Share on other sites More sharing options...
Aaron M. Posted September 8, 2019 Share Posted September 8, 2019 Facing a similar issue with 2.3.2.56 where I am unable to access port 5000 on my Synology Diskstation. I'm on CenturyLink with VLAN tagging enabled and this is an absolute pain as I'm also unable to back up my MacBook via Time Machine as it never connects. What are next steps...? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted September 8, 2019 Administrators Share Posted September 8, 2019 24 minutes ago, Aaron M. said: Facing a similar issue with 2.3.2.56 where I am unable to access port 5000 on my Synology Diskstation. I'm on CenturyLink with VLAN tagging enabled and this is an absolute pain as I'm also unable to back up my MacBook via Time Machine as it never connects. What are next steps...? Hey, welcome to the forum! Looking at the topic it's something Netgear are aware of and need to fix. If you could get another router to handle VLAN so the XR500 doesn't then that would work but nothing else you could do at the moment. Link to comment Share on other sites More sharing options...
Aaron M. Posted September 11, 2019 Share Posted September 11, 2019 On 9/8/2019 at 1:06 PM, Netduma Fraser said: Hey, welcome to the forum! Looking at the topic it's something Netgear are aware of and need to fix. If you could get another router to handle VLAN so the XR500 doesn't then that would work but nothing else you could do at the moment. Thanks for the update. I actually purchased the XR500 to remove a CenturyLink router in concert with a TP-LINK, so that I could have one router own it all. The testing you referred to back in late July, is that still underway? Assuming that's not the version I am on...? Link to comment Share on other sites More sharing options...
Netduma Alex Posted September 11, 2019 Share Posted September 11, 2019 Yes I believe it's still underway. Link to comment Share on other sites More sharing options...
Aaron M. Posted October 27, 2019 Share Posted October 27, 2019 Same story...? Link to comment Share on other sites More sharing options...
Aaron M. Posted November 17, 2019 Share Posted November 17, 2019 Still routine issues with this router. Any word on an update...? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 17, 2019 Administrators Share Posted November 17, 2019 22 minutes ago, Aaron M. said: Still routine issues with this router. Any word on an update...? I will ask Alex but I assume he has been busy trying to make CoD as compatibile as possible with the cloud. Link to comment Share on other sites More sharing options...
Netduma Alex Posted November 18, 2019 Share Posted November 18, 2019 Unfortunately this really is a problem that only NETGEAR can sort out, as it pertains specifically to their section of the firmware. I will however contact them to confirm that they're aware of this issue. Link to comment Share on other sites More sharing options...
Guest Killhippie Posted November 18, 2019 Share Posted November 18, 2019 49 minutes ago, Netduma Alex said: Unfortunately this really is a problem that only NETGEAR can sort out, as it pertains specifically to their section of the firmware. I will however contact them to confirm that they're aware of this issue. Don't hold your breath, Alex. Link to comment Share on other sites More sharing options...
Aaron M. Posted November 30, 2019 Share Posted November 30, 2019 @Netduma Alex Appreciate the response. Interestingly enough, this issue also affects my Philips Hue bridge and the ability for the mobile app to connect and control the lights. I've read the handful of other posts on the topic and I'm 100% certain that the common underlying issue is anyone making use of the VLAN 201 tagging with Century Link. Perhaps we can refocus efforts on that specific set up? I'm hesitant to open a case since I witnessed someone else go through that exercise in another thread to no avail and knowing that VLAN 201 tagging is the culprit, we need a developer to take a look! Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted November 30, 2019 Administrators Share Posted November 30, 2019 That's very interesting thank you for the information, that is something that would require Netgear to look at as we don't cover that aspect of the router. I would suggest you make a case and then we can push them from our side as well. It's more to make them aware rather than expecting a quick fix as it will require a dev to fix it. Link to comment Share on other sites More sharing options...
Aaron M. Posted December 4, 2019 Share Posted December 4, 2019 On 11/30/2019 at 8:41 AM, Netduma Fraser said: That's very interesting thank you for the information, that is something that would require Netgear to look at as we don't cover that aspect of the router. I would suggest you make a case and then we can push them from our side as well. It's more to make them aware rather than expecting a quick fix as it will require a dev to fix it. Case number is: 41993256 Calling in was an absolute nightmare so anything you can do to help -- thank you in advance! Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 4, 2019 Administrators Share Posted December 4, 2019 3 hours ago, Aaron M. said: Case number is: 41993256 Calling in was an absolute nightmare so anything you can do to help -- thank you in advance! Sorry to hear that but thank you for the number. I've asked our team to push NG on this case. Link to comment Share on other sites More sharing options...
Aaron M. Posted December 9, 2019 Share Posted December 9, 2019 On 12/4/2019 at 11:12 AM, Netduma Fraser said: Sorry to hear that but thank you for the number. I've asked our team to push NG on this case. Any movement by chance? 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