Ford Fairlane 11 Posted January 20 Author Posted January 20 25 minutes ago, sa2000 said: Logs are retained for 3 days. This can be extended by editing system.xml The log you attached covers the 19th of January (period covered 2026-01-18 23:59 to 2026-01-19 23:59) The log does not show removals from the library as was seen before - eg beforehand we had log entries like these: 2025-12-11 08:11:45.281 Info App: Removing item from database, Type: Series, Name: The Simpsons, Path: smb://192.168.0.112/Tv/The Simpsons, Id: 243439 2025-12-11 08:11:46.828 Info App: Removing item from database, Type: Series, Name: American Dad!, Path: smb://192.168.0.112/Tv/American Dad, Id: 243440 No removals in the log for the 19th January. Two issues show in the log 1. Running out of disk space of the QNAP - that could affect the operation of Emby Server. This shows you were down to about 53Mb free space on the QNAP filesystem 2026-01-19 20:59:46.494 Info EncodingManager: Deleting segment /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/transcoding-temp/CD5A04/CD5A04_0.ts due to disk space. Available space: 56004608 You can see that log line shows Available space: 56004608 2. Failures during probing the media files for S11 of Robot Chicken - there were being checked on the smb path - so the path was available. But the same ffprobe errors were logged later on probing the backup files on /Multimedia/TV Backup/ path on the QNAP - so suspect the files were invalid But the log shows the smb path to 192.168.0.112/Tv accessible throughout the 19th January When did the libraries disappear ? hi the qnap isnt hosting the TV folder, the tv folder is stored on an WD ex2 ultra "2. Failures during probing the media files for S11 of Robot Chicken - there were being checked on the smb path - so the path was available. But the same ffprobe errors were logged later on probing the backup files on /Multimedia/TV Backup/ path on the QNAP - so suspect the files were invalid" thats a backup folder for tv that i created due to the constant problems with the Tv folder folders disappearing, the backup folder never shows as empty even with errors ive got about 3.6 tb space on the qnap, any idea where this storage reading is from?
sa2000 673 Posted January 20 Posted January 20 (edited) 14 minutes ago, Ford Fairlane said: ive got about 3.6 tb space on the qnap, any idea where this storage reading is from? Can you get me the output from df command in an ssh session on the QNAP The log entries were relating to this path /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/ 14 minutes ago, Ford Fairlane said: the qnap isnt hosting the TV folder, the tv folder is stored on an WD ex2 ultra Yes - I am aware that the TV Shows library media is from "smb://192.168.0.112/Tv" Library: TV shows, id: 192737, CollectionType: tvshows, CollapseSingleItemFolders: False, ForceCollapseSingleItemFolders: False Configured paths: smb://192.168.0.112/Tv Library Folder: Tv, id: 192739: path: smb://192.168.0.112/Tv The log for the 19th January that you provided does not show any media disappeared (removed) from the library What time / day did the library view show no media files? Edited January 20 by sa2000
Ford Fairlane 11 Posted January 20 Author Posted January 20 18 minutes ago, sa2000 said: Can you get me the output from df command in an ssh session on the QNAP The log entries were relating to this path /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/ Yes - I am aware that the TV Shows library media is from "smb://192.168.0.112/Tv" Library: TV shows, id: 192737, CollectionType: tvshows, CollapseSingleItemFolders: False, ForceCollapseSingleItemFolders: False Configured paths: smb://192.168.0.112/Tv Library Folder: Tv, id: 192739: path: smb://192.168.0.112/Tv The log for the 19th January that you provided does not show any media disappeared (removed) from the library What time / day did the library view show no media files? Yes - I am aware that the TV Shows library media is from "smb://192.168.0.112/Tv" was just mentioning as you were mentioning a different tv folder, just making sure. its happened between, 9pm and 9am
sa2000 673 Posted January 20 Posted January 20 9 minutes ago, Ford Fairlane said: 9pm and 9am 9pm 18th January to 9am 19th January or 9pm 19th January to 9am 20th January Either way - i do not have log files for the whole period
Ford Fairlane 11 Posted January 20 Author Posted January 20 58 minutes ago, sa2000 said: 9pm 18th January to 9am 19th January or 9pm 19th January to 9am 20th January Either way - i do not have log files for the whole period 9pm 19th January to 9am 20th January thats why i believe it wont appear till tonights log file at 23;59 this is log file from when i restored to see if i could recover this afternoon. embyserver-63904508982.txt
sa2000 673 Posted January 20 Posted January 20 37 minutes ago, Ford Fairlane said: 9pm 19th January to 9am 20th January thats why i believe it wont appear till tonights log file at 23;59 this is log file from when i restored to see if i could recover this afternoon. It happened at 11:49 am on the 20th - starting at this time 2026-01-20 11:49:06.363 Info App: ValidatePhysicalRoots start validating 192739 Tv smb://192.168.0.112/Tv 2026-01-20 11:49:11.515 Info App: Removing item from database, Type: Series, Name: The Simpsons, Path: smb://192.168.0.112/Tv/The Simpsons, Id: 278843 No indication in the log as to why. A similar action the day before did not remove the paths from the database 2026-01-19 11:49:29.616 Info App: ValidatePhysicalRoots start validating 192739 Tv smb://192.168.0.112/Tv You then restored the database at 12:26 Maybe enabling debug logging would have extra clues for next time it happens the only errors relating to the network are much earlier relating to 239.255.255.250:1900 being unreachable. I don't know if the underlying reason for these errors affects smb operation in anyway - but it was the first scan after these errors Example: 2026-01-20 02:44:07.042 Error App: Error sending socket message from 0.0.0.0:1900 to 239.255.255.250:1900 System.Net.Sockets.SocketException: System.Net.Sockets.SocketException (101): Network is unreachable This shows 3 scans with the 3rd one removing the media items from the database 2026-01-19 11:49:29.616 Info App: ValidatePhysicalRoots start validating 192739 Tv smb://192.168.0.112/Tv 2026-01-19 11:55:04.717 Info App: ValidatePhysicalRoots completed validating 192739 Tv smb://192.168.0.112/Tv 2026-01-19 23:49:23.158 Info App: ValidatePhysicalRoots start validating 192739 Tv smb://192.168.0.112/Tv 2026-01-19 23:54:44.980 Info App: ValidatePhysicalRoots completed validating 192739 Tv smb://192.168.0.112/Tv 2026-01-20 11:49:06.363 Info App: ValidatePhysicalRoots start validating 192739 Tv smb://192.168.0.112/Tv 2026-01-20 11:49:11.515 Info App: Removing item from database, Type: Series, Name: The Simpsons, Path: smb://192.168.0.112/Tv/The Simpsons, Id: 278843 2026-01-20 11:49:15.016 Info App: Removing item from database, Type: Series, Name: American Dad!, Path: smb://192.168.0.112/Tv/American Dad, Id: 278844 . . . etc . . . in total 189 shows removed from the database 2026-01-20 11:49:59.914 Info App: Removing item from database, Type: Folder, Name: Derry Gi, Path: smb://192.168.0.112/Tv/Derry Gi, Id: 279031 2026-01-20 11:50:00.063 Info App: ValidatePhysicalRoots completed validating 192739 Tv smb://192.168.0.112/Tv May require adding additional logging - cc @Luke
Ford Fairlane 11 Posted January 20 Author Posted January 20 (edited) Maybe enabling debug logging would have extra clues for next time it happens the only errors relating to the network are much earlier relating to 239.255.255.250:1900 being unreachable. I don't know if the underlying reason for these errors affects smb operation in anyway - but it was the first scan after these errors ive enabled debug logging. i dont recognise that ip, do you reckon it could be the smb ip? as the wd mycloud ip is different it was never and issue till about version 1.8 ish. previously it would remove everything, then i disabled real time monitoring and was fine, then a few updates later it was just constantly removing everything Also what is making it validate the drive if real time monitoring is disabled? Edited January 20 by Ford Fairlane
sa2000 673 Posted January 20 Posted January 20 (edited) 7 minutes ago, Ford Fairlane said: dont recognise that ip, do you reckon it could be the smb ip? The messages to 239.255.255.250:1900 are SSDP broadcasts / multicasts Is there a firewall running on the QNAP? 7 minutes ago, Ford Fairlane said: it was never and issue till about version 1.8 ish. previously it would remove everything, then i disabled real time monitoring and was fine, then a few updates later it was just constantly removing everything There were library scans at 11:49 and 23:49 which suggested you had scheduled library scans every 12 hours But the issue did not arise in 2 of the 3 scans in the log. Either way, Emby Server should not be removing the media items, See if there is a firewall running on the QNAP and if there was any logging Edited January 20 by sa2000
Neminem 1515 Posted January 20 Posted January 20 22 minutes ago, Ford Fairlane said: the only errors relating to the network are much earlier relating to 239.255.255.250:1900 being unreachable. Do you have DLNA or UPNP plugin installed. Those plugin might be the reason for those errors. 1
Happy2Play 9780 Posted January 20 Posted January 20 (edited) 56 minutes ago, Ford Fairlane said: the only errors relating to the network are much earlier relating to 239.255.255.250:1900 being unreachable. This is only related to DLNA as that is what runs on port 1900 and does not work on all setups. But can guess there are still issues with using smb paths on some setups. Even though fixes have been added in 4.8/4.9 updates. As previously these paths were not recommended. Edited January 20 by Happy2Play 1
fordfairlane 2 Posted January 20 Posted January 20 2 hours ago, Neminem said: Do you have DLNA or UPNP plugin installed. Those plugin might be the reason for those errors. They are enabled and have been installed way before this issue began. 1
Neminem 1515 Posted January 20 Posted January 20 @sa2000guess you need more logs, to see the issue. Since these requests are related to DLNA.
fordfairlane 2 Posted January 20 Posted January 20 8 minutes ago, Neminem said: @sa2000guess you need more logs, to see the issue. Since these requests are related to DLNA. But how or why would a dlna request delete the library? I'll disable them and the firewall to see if that makes a difference
Neminem 1515 Posted January 20 Posted January 20 2 minutes ago, fordfairlane said: But how or why would a dlna request delete the library? They should / would not 2 minutes ago, fordfairlane said: I'll disable them and the firewall to see if that makes a difference Then that should produce clean logs
sa2000 673 Posted January 20 Posted January 20 2 minutes ago, fordfairlane said: But how or why would a dlna request delete the library I never said - I said the underlying cause may be a factor / the network unreachable error I would like to establish if there is a firewall on the QNAP and if disabling has an impact on the issue
Ford Fairlane 11 Posted January 21 Author Posted January 21 ive turned off smb service and firewall. almost 24hrs since i did recovery and folder still populated 1
sa2000 673 Posted January 21 Posted January 21 Is that a firewall on the QNAP ? Does it have any logging?
sa2000 673 Posted January 21 Posted January 21 46 minutes ago, Ford Fairlane said: almost 24hrs since i did recovery and folder still populated do you still have the scans every 12 hours ? If not, could you go scheduled tasks and run a scan media library to see if that is ok - would not be conclusive because we had previously 3 scans with only losing the media after the third - possibly after a network / firewall block overnight
Happy2Play 9780 Posted January 21 Posted January 21 3 hours ago, Ford Fairlane said: ive turned off smb service almost 24hrs since i did recovery and folder still populated Not sure how libraries are working if you disable the service they are being shared on. There are many older topics where smb has always had issues like this on some setups and Luke always suggested. Quote Instead, mount the network path to a local path using the tools in your host OS. Then import that local path into Emby Server. 1
Ford Fairlane 11 Posted January 22 Author Posted January 22 20 hours ago, sa2000 said: Is that a firewall on the QNAP ? Does it have any logging? seems to have limited logging based on the file do you still have the scans every 12 hours ? If not, could you go scheduled tasks and run a scan media library to see if that is ok - would not be conclusive because we had previously 3 scans with only losing the media after the third - possibly after a network / firewall block overnight disabled all scanning Not sure how libraries are working if you disable the service they are being shared on. There are many older topics where smb has always had issues like this on some setups and Luke always suggested. glad you mentioned that, as ive disabled the qnap smb but forgot the wd mycloud smb is still running. There are many older topics where smb has always had issues like this on some setups and Luke always suggested. tried that as well same result, again this has only happened in the last 8-12 months before that no problems with libraries. so far library is still populated QuFirewall_Q217I00103_20260122.zip
sa2000 673 Posted January 22 Posted January 22 52 minutes ago, Ford Fairlane said: QuFirewall_Q217I00103_20260122.zip 4.44 kB · 0 downloads This confirms it was the QNAP QuFirewall that was blocking the UDP SSDP / Broadcasts/Multicasts to 239.255.255.250 on port 1900 e.g. Jan 20 02:46:47 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=57194 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 Jan 20 02:46:47 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=57194 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 Jan 20 02:46:48 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=155 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=46735 DPT=1900 LEN=135 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=239.255.255.250 LEN=156 TOS=00 PREC=0x00 TTL=4 ID=36235 DF PROTO=UDP SPT=49155 DPT=1900 LEN=136 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=239.255.255.250 LEN=156 TOS=00 PREC=0x00 TTL=4 ID=36237 DF PROTO=UDP SPT=49155 DPT=1900 LEN=136 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=239.255.255.250 LEN=156 TOS=00 PREC=0x00 TTL=4 ID=36243 DF PROTO=UDP SPT=49155 DPT=1900 LEN=136 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=239.255.255.250 LEN=156 TOS=00 PREC=0x00 TTL=4 ID=36248 DF PROTO=UDP SPT=49155 DPT=1900 LEN=136 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=239.255.255.250 LEN=156 TOS=00 PREC=0x00 TTL=4 ID=36252 DF PROTO=UDP SPT=49155 DPT=1900 LEN=136 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=36840 DF PROTO=UDP SPT=56700 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=36841 DF PROTO=UDP SPT=56700 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=36842 DF PROTO=UDP SPT=56700 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=36843 DF PROTO=UDP SPT=39346 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=47949 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=47949 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=36852 DF PROTO=UDP SPT=53246 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=36853 DF PROTO=UDP SPT=53246 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=36854 DF PROTO=UDP SPT=53246 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=36855 DF PROTO=UDP SPT=46812 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:51 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=50343 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 Jan 20 02:46:51 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=239.255.255.250 LEN=358 TOS=00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=50343 DPT=1900 LEN=338 UID=0 GID=0 MARK=0 also broadcasts to 255.255.255.255 Jan 20 02:47:08 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:50:b0:3b:e3:9a:51:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=00 PREC=0x00 TTL=16 ID=7890 PROTO=UDP SPT=68 DPT=67 LEN=308 MARK=0 Jan 20 02:47:08 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:50:b0:3b:e3:9a:51:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=00 PREC=0x00 TTL=16 ID=52120 PROTO=UDP SPT=68 DPT=67 LEN=308 MARK=0 Jan 20 02:48:05 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:92:c0:d3:96:0e:3e:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=342 TOS=10 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=322 MARK=0 Jan 20 02:48:28 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:92:01:37:69:78:7e:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=342 TOS=10 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=68 DPT=67 LEN=322 MARK=0 Jan 20 02:48:51 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:64:5a:ed:e8:95:93:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=328 TOS=00 PREC=0x00 TTL=255 ID=22625 PROTO=UDP SPT=68 DPT=67 LEN=308 MARK=0 Does not show any other blocked packets - so not sure if it affected the smb paths. You could try re-enabling SMB but disabling the QuFirewall and see what happens
Ford Fairlane 11 Posted January 22 Author Posted January 22 so the firewall seems to be causing the issue, but why would it create a problem on a random scan when previous scans passed fine?
sa2000 673 Posted January 22 Posted January 22 4 minutes ago, Ford Fairlane said: but why would it create a problem on a random scan when previous scans passed fine? strange. And the firewall log does not show any blocked packets relating to 192.168.0.112 (the WD NAS) Would probably need some extra logging in Emby Server The log shows some more blocked packets - mDNS packets to port 5353 for 224.0.0.251 eg Jan 20 02:46:27 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=45:00:01:08:49:2d:40:00:ff:11:8f:30:c0:a8 SRC=192.168.0.227 DST=224.0.0.251 LEN=264 TOS=00 PREC=0x00 TTL=255 ID=18733 DF PROTO=UDP SPT=5353 DPT=5353 LEN=244 MARK=0 Jan 20 02:46:27 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:00:00:fb:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=224.0.0.251 LEN=247 TOS=00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=59633 DPT=5353 LEN=227 UID=65534 GID=65534 MARK=0 Jan 20 02:46:27 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:00:00:fb:74:ee:2a:e7:24:b1:08:00 SRC=192.168.0.22 DST=224.0.0.251 LEN=247 TOS=00 PREC=0x00 TTL=1 ID=0 DF PROTO=UDP SPT=59633 DPT=5353 LEN=227 UID=65534 GID=65534 MARK=0 Jan 20 02:46:27 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=45:00:01:08:4a:25:40:00:ff:11:8e:38:c0:a8 SRC=192.168.0.227 DST=224.0.0.251 LEN=264 TOS=00 PREC=0x00 TTL=255 ID=18981 DF PROTO=UDP SPT=5353 DPT=5353 LEN=244 MARK=0 Also these requests from a Philips TV on 192.168.0.24 to the server Jan 20 02:46:39 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=24:5e:be:65:f1:cd:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=192.168.0.227 LEN=60 TOS=00 PREC=0x00 TTL=64 ID=41513 DF PROTO=TCP SPT=56614 DPT=8096 SEQ=2882308700 ACK=0 WINDOW=65535 SYN URGP=0 MARK=0 Jan 20 02:46:40 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=24:5e:be:65:f1:cd:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=192.168.0.227 LEN=60 TOS=00 PREC=0x00 TTL=64 ID=41514 DF PROTO=TCP SPT=56614 DPT=8096 SEQ=2882308700 ACK=0 WINDOW=65535 SYN URGP=0 MARK=0 Jan 20 02:46:42 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=24:5e:be:65:f1:cd:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=192.168.0.227 LEN=60 TOS=00 PREC=0x00 TTL=64 ID=41515 DF PROTO=TCP SPT=56614 DPT=8096 SEQ=2882308700 ACK=0 WINDOW=65535 SYN URGP=0 MARK=0 Jan 20 02:46:46 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=24:5e:be:65:f1:cd:dc:72:23:bd:58:fa:08:00 SRC=192.168.0.24 DST=192.168.0.227 LEN=60 TOS=00 PREC=0x00 TTL=64 ID=41516 DF PROTO=TCP SPT=56614 DPT=8096 SEQ=2882308700 ACK=0 WINDOW=65535 SYN URGP=0 MARK=0
sa2000 673 Posted January 22 Posted January 22 These SSDP requests from the WD NAS were blocked Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=34762 DF PROTO=UDP SPT=46068 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=34763 DF PROTO=UDP SPT=46068 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=34764 DF PROTO=UDP SPT=46068 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=34765 DF PROTO=UDP SPT=37695 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=34773 DF PROTO=UDP SPT=45226 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=34774 DF PROTO=UDP SPT=45226 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=34775 DF PROTO=UDP SPT=45226 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:10 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=34776 DF PROTO=UDP SPT=36151 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:28 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=34910 DF PROTO=UDP SPT=50876 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:28 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=34911 DF PROTO=UDP SPT=50876 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:28 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=34912 DF PROTO=UDP SPT=50876 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=35037 DF PROTO=UDP SPT=59966 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=35038 DF PROTO=UDP SPT=59966 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=35039 DF PROTO=UDP SPT=59966 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=35040 DF PROTO=UDP SPT=55006 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=35047 DF PROTO=UDP SPT=59264 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=35048 DF PROTO=UDP SPT=59264 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=35049 DF PROTO=UDP SPT=59264 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=35050 DF PROTO=UDP SPT=49432 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=35074 DF PROTO=UDP SPT=59146 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=35075 DF PROTO=UDP SPT=59146 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:30 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=160 TOS=00 PREC=0x00 TTL=1 ID=35076 DF PROTO=UDP SPT=59146 DPT=1900 LEN=140 UID=0 GID=0 MARK=0 Jan 20 02:46:32 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=161 TOS=00 PREC=0x00 TTL=1 ID=35247 DF PROTO=UDP SPT=35361 DPT=1900 LEN=141 UID=0 GID=0 MARK=0 Jan 20 02:46:32 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=161 TOS=00 PREC=0x00 TTL=1 ID=35248 DF PROTO=UDP SPT=35361 DPT=1900 LEN=141 UID=0 GID=0 MARK=0 Jan 20 02:46:32 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=161 TOS=00 PREC=0x00 TTL=1 ID=35249 DF PROTO=UDP SPT=35361 DPT=1900 LEN=141 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=36840 DF PROTO=UDP SPT=56700 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=36841 DF PROTO=UDP SPT=56700 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=36842 DF PROTO=UDP SPT=56700 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=36843 DF PROTO=UDP SPT=39346 DPT=1900 LEN=498 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=468 TOS=00 PREC=0x00 TTL=4 ID=36852 DF PROTO=UDP SPT=53246 DPT=1900 LEN=448 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=477 TOS=00 PREC=0x00 TTL=4 ID=36853 DF PROTO=UDP SPT=53246 DPT=1900 LEN=457 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=522 TOS=00 PREC=0x00 TTL=4 ID=36854 DF PROTO=UDP SPT=53246 DPT=1900 LEN=502 UID=0 GID=0 MARK=0 Jan 20 02:46:50 NAS65F1CD RULE=3 ACT=DROP IN=eth0 OUT= MAC=01:00:5e:7f:ff:fa:00:00:c0:39:6c:61:08:00 SRC=192.168.0.112 DST=239.255.255.250 LEN=518 TOS=00 PREC=0x00 TTL=4 ID=36855 DF PROTO=UDP SPT=46812 DPT=1900 LEN=498 UID=0 GID=0 MARK=0
Ford Fairlane 11 Posted January 22 Author Posted January 22 ive recently changed to a new router, could this be possibly causing an issue. the qnap and wd are wired connections to router. one thing ive just remembered i had an issue couple of years ago with the WD was it would for some reason go from a local disk to a not being recognised as a local disk
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