dinth
Dialled in
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: UniFi setup with VM
Thats not true. The SuperHub is still running a DHCP server server which will be confusing the router. It can be easily checked by connecting a laptop to SH in modem mode - the laptop will still receive DHCP lease. This causes massive problems with routing software like pfSense and opnSense - although it can be easily fixed by setting up the router to reject leases coming from 192.168.100.1 - SuperHub internal address. It will also cause problems with Unifi equipment, as it cannot be set to reject leases from a particular IP.136Views0likes1CommentRe: UDP issues on SuperHub3 - collective thread
Andrew-G wrote: My point still stands - that there's no difference in the service customers get from a Hub 3 as they would see from a Hub 5. What chipset does SH5 use? Because contrary to what you are saying, there are users who had SH3/4 replaced with SH5 resolving their UDP traffic issues Andrew-G wrote: alleged You keep using this word, but the issue has been confirmed and replicated by dozens of users just in this thread. Not to mention hundreds of threads on this forum describing similar problems and never getting resolved by VM.2.2KViews2likes9CommentsRe: UDP issues on SuperHub3 - collective thread
Andrew-G wrote: What leads you to think the Hub 5 is better? Reports from users who had SH3 upgraded to SH5 earlier in this thread. Andrew-G wrote: DOCSIS is adequate for all purposes, but is not and never will be the best technology for more demanding uses. Anybody who honestly believes that a Hub 5 will solve perceived problems (other than as a placebo) is kidding themselves, and either needs to accept it for what it is, or get themselves a VDSL or genuine PON connection. VM will eventually provide PON...for those willing to wait some years. The issue which is being discussed here has literally nothing to do with a connection itself, but the (hardware?) bug in SH3/4 modems provided by VM. From my experience, VM DOCSIS is good enough even for very demanding (selfhosting, etc) user, as tested on SH2. Problems started when my modem was upgraded to SH3.2.2KViews2likes12CommentsRe: UDP issues on SuperHub3 - collective thread
The only real cure is SH5. Even putting the modem in router mode as a workaround doesn't completely fix the problem. Sure UDP does no longer completely kill the modem but still seeing some weird fluctuations during heavy UDP use2.2KViews1like14CommentsRe: UDP issues on SuperHub3 - collective thread
Hi Kath. Nice to see that someone from VM staff actually reads this topic, but im afraid that your offer to help is just meant to take discussion about @janskit issue offline. I have been very vocal about this issue since i upgraded to SH3 a few years ago and here we are, few years have passed, i have made countless escalations - including the regulatory body which gave you a set time to resolve my issue and you failed to that - and yet, my issue is still not resolved. Same story with dozens of other users in this thread and potentially hundreds of users who dont know about this thread. Your users have actually done all the work here, found an issue, came up with a troubleshooting procedure that can be used to confirm the issue, ways of reproducing the issue and even told you what you need to do to fix the issue - which is swapping the modem for SH2 or SH5. And yet, VM is still refusing to do that, probably because you dont want to acknowledge that there was an issue with SH3/4 in the first place. Kind regards1.8KViews4likes2Comments