PfSense wakes my Synology NAS boxes from hibernation every 1 hour….
-
Hi, Guys
Just setup my pfSense (2.2.2) with SNORT + pfBlockerNG installed for fun for home use, I'm a noob to pfSense, so far its running great except that it automatcally wakes up my 2 Synology NAS boxes every 1 hour, which is crazy. I had 2 routers that both connected to the internet, if the NAS connect to Netgear R7000 (DD-WRT), no auto wakes-up, but as long as plugged the NAS in pfSense router, my NAS boxes (both setup to has static Lan IP) will be waken up every 1 hour. I must missing some of the setup settings, but can't figure it out. What I do notice from System logs/DHCP is that when every time there is:
dhcpd: DHCPACK on <my nas="" lan="" ip="">to <my nas="" mac="" addr="">via em1
dhcpd: DHCPREQUEST <my nas="" lan="" ip="">from <my nas="" mac="" addr="">via em1It wakes up my NAS server from hibernation. so I need some helps to fix it, Thanks.</my></my></my></my>
-
Your NAS sending a DHCPREQUEST is probably a symptom of it waking up, not a cause.
Me? I'd put the NAS on a mirror port on my switch, let it sleep, then run a packet capture until it's woken up and see what caused it.
-
I'd put the NAS on a mirror port on my switch, let it sleep, then run a packet capture until it's woken up and see what caused it.
How to do these? Please excuse my noob questions.
-
I'm actually in the process of doing this but in a rather complex way for different reasons.
I got a MikroTik RB260GS 5-port switch to do the mirroring. You can get one off of Amazon for about $40. Tiny device but with lots of networking features for a very low cost.
You'd connect your switch to the MikroTik on one port, and then your NAS on the other port. Then on a third port you'd connect a computer that would do the packet capture. You'd mirror the ingress and egress of either of the two ports (the one to your switch or NAS) to the third port with the packet capture computer (server). This way it will inconspicuously capture all of the traffic and analyze it for you.
In my particular case, I am building a Security Onion server to do the packet capture and analysis. It's not for the faint of heart, but IMHO it's a power suite of tools that is worth learning about. All open source, widely supported, and very good at what they do. SO has some heavy requirements, but if you're using it for home the thing you'll be most concerned about is disk space. More disk, more historical data before the system prunes it.
Once you have everything set up, you can check the packet capture and logs (yes, SO will also function as a centralized logging server) to see of you can correlate the wake-up event to a trigger.
That's one way to do it, and there are many more ways to do the same. Just wanted to share my approach, which may be overkill for what you want to do.
-
…
my NAS boxes (both setup to has static Lan IP) will be waken up every 1 hour. I must missing some of the setup settings
...Services: DHCP server:
NAS has a number outside the pool ?
Created in Static Mappings ? -
-
@hda:
…
my NAS boxes (both setup to has static Lan IP) will be waken up every 1 hour. I must missing some of the setup settings
...NAS has a number outside the pool ?
Here is what my DHCP Server settings is:
Available range 192.168.1.1 - 192.168.1.254
Range 192.168.1.2 - 192.168.1.50My NAS static mappings is 192.168.1.107
Am I doing some wrong here? is it outside the pool? Thanks.
-
I sent my nas hibernation debug logs to the Synology tech support, and here is what they replied:
Based on the output you provided it appears that the router keeps trying to distribute DHCP addresses to the units, even though they already have an IP address. A simple way to test this is to try unplugging the DiskStations from the network thereby isolating them from the router. They should then stay in hibernation.
Unfortunately if the router keeps trying to hand out an IP address, there's not much that can be done from the DiskStation side. You can try setting a manual IP address, but it would be best to use one from outside of the router DHCP pool.
Here is what my DHCP Server settings is:
Available range 192.168.1.1 - 192.168.1.254
Range 192.168.1.2 - 192.168.1.50My NAS static mapping/lease is 192.168.1.107
How should I do to fix it?
-
Avoid the NAS IP taken into the lease renewal.
Your pool/range seems to be .2 to .50, so yes your .107 should be outside the pool.
Did you create .107 with the mac in "Services: DHCP server" (bottom page)?[You should see the static in the list with "Status: DHCP leases"]
I myself reserve low numbers for static entries and have a range/pool .101 to .200
-
@hda:
Avoid the NAS IP taken into the lease renewal.
Your pool/range seems to be .2 to .50, so yes your .107 should be outside the pool.
Did you create .107 with the mac in "Services: DHCP server" (bottom page)?I myself reserve low numbers for static entries and have a range/pool .101 to .200
Yes. I create .107 with the NAS mac address under the bottom of DHCP Server/Lan, and my NAS did get that lan ip address, How to avoid the NAS IP taken into the lease renewal? all were blank by default.
-
Suggestion recreate: manual input a new IP (say .101) on both sides: NAS-side & pfSense-side.
-
No. Didn't work, re-created it, but still wake up after 1 hour, but I only created it at pfSense side. would try to enter the manual IP, rather than auto DHCP, at the NAS side
-
Me? I'd put the NAS on a mirror port on my switch, let it sleep, then run a packet capture until it's woken up and see what caused it.
Why guess at the problem?
-
Agreed take a sniff and see exactly what is causing a wake up.
-
Agreed take a sniff and see exactly what is causing a wake up.
As my NAS hibernation logs tells, also from Synology tech support:
It appears that the router keeps trying to distribute DHCP addresses to the units, even though they already have an IP address.
I'm not sure its the NAS problem or pfSense problem, NAS is sending DHCPREQUEST command to pfSense every 1 hour, but if the lease time isn't expired, Shouldn't pfSense NOT distribute DHCP address to the unit?
-
It appears that the router keeps trying to distribute DHCP addresses to the units, even though they already have an IP address.
Yes, of course, the DHCP server keeps "distributing" IP address requested by your NAS, kindly cf.
dhcpd: DHCPREQUEST <my nas="" lan="" ip="">from <my nas="" mac="" addr="">via em1</my></my>Also, the DHCP leases expire and need to get renewed (after a configurable period. check the GUI). So yeah, this will happen "even though they already have an IP address", perhaps the Synology support could educate themselves a bit.
Finally, if you do not want DHCP, then configure a static IP on your NAS and move on!
-
… but I only created it at pfSense side ...
Before you jump in mirroring investigation, if you know-how. I am not sure if you are exact & correct. You really should test giving the NAS a new number manually (outside the range/pool) AND manually input it in pfSense too.
This is to assure yourself the volatile memory about .107 is flushed on both sides… Maybe even reboot both hardware. -
Yes. It should not be a DHCP static mapping. That still has to periodically renew. It should be a static IP address directly configured on the NAS, outside the DHCP pool.
-
What dhcp server doesn't just out of the blue send out hey you want to renew your lease packets.. But if it gets a request then yeah it will send back something..
Tell their their Tech Support to tell you how not to send a request.. What is the lease time to start with 2 hours? Normally a dhcp client will request renewal of its lease at the 50% mark. So if you want the nas not to request, then it should be long lease. If the device is in standby/sleep why would it send out a dhcprequest is the question I would have.
-
True. Should stop guessing and sniff.
