![]() as you can see i am stuck between a rock and synology 'hard place' support.ģ mins untill the nat-pmp needs to refresh. So i am not even clear that the router is at fault - though synology claim it is removing ACTIVE port mappings every 3 to 5 minutes. If i go back to the synology and make one change to one rule and click save then all the rules get rewitten and every thiung works ok. what is odd is once the mappings break they still appear in the asus UI they just don't work. Turns out they just set the re advertisement of unpnp to less than an hour now they are saying they have had to change it to every 60 seconds for the port mappings to stay working. I had the issue last year - there is a thread around here somewhere and back then they 'fixed' it. I should also be clearer that the port mapping of plex (running on the synology and using its own code) and the auto mapping of the asus router HTTPD (yes i know this is a silly idea) all work PERFECTLY its only the synology thats at issue. The upnp wizard on synology has a maximum of 100 - my point being only that a synology could be doing many if VPN, mailservers, couchh potato, whatever is running and that with other devices in my house a fixed 20 might be an issue. It is creating around 15 actively used ones (like port 25 for my mail server) of them, plus i have others from plex and stuff. In the mean time i am seeing if i can futz with the synology conf files to use nat-pmp.Ĭlick to expand.I don't think it is your fault, my poor lack of words. For example i know their workaround of getting the router to refresh every 60 seconds is inelegant at best. I am more than willing to go back to synology and argue the point if someone can help me determine very specifically what synology is doing wrong. If it only occurs on merlin firmware (and not latest stock firmware) and it is not occurring on other routers (both of which synology are claiming) it is a little hard for me to persuade them to make a change and a little hard for me to argue to them that whomever made this implementation choice on asus/merlin was right. To be clear why i am asking - synology support is a royal PITA, my goal is to be sure that if it is the synology that should be changing i have cast iron explanation of what they need to do and a good reason like "hey synology as all routers move to minupnpd 2.0 you are gonna have this problem". I am questioning if the conf file parameters make sense given they 'apparently' were different a year ago (less aggressive) and are certainly not the default for minupnpd. I agree the router is behaving as expected per the conf file. I would like to tell them what a best practice approach to fixing this would be.Ĭlick to expand.Who says? It seems to be different behaviour from a year ago according to synology (not that i am willing to take that to the bank ). And what, if anything, i shoud tell them to change about the implementation.īTW the have changed a file on the NAS called /etc/portforwarding/pfd.config to re-register every 2 minutes with a caveat that this breaks their hibernation support. Given that no other services behind my router are having this issue (emby, plex, etc etc) i suspect synology need to change their implementation assumptions but i don't know what to tell them.ĭoes anyone know what the behavior of miniupnpd is supposed to be in terms of leases, lease defaults, infinite leases and scrubbing of leases. They state that last year the router cleared upnp leases every hour (they increased the frequency of their upnp code making leases on my NAS to less than an hour) and that now the router running the latest FW is clearing leases every 3 to 5 minutes. I upgraded their SW and the same issue came back, after much cajoling (their quality of support has deteriorated in the last year) they connected and looked at why the issue came back. (i can get exact date of issue if we need to track back to specific older fimrware). Synology connected remotel to my NAS and 'fixed it'. I had issues last year with earlier fimrware and synology NAS where the NAS couldn't keep its outbound mappings open. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |