Pfsense <-> solaredge
-
Hmm, weird that it happens after 3 days… Like maybe it's cached something and only has to re-resolve it then.
How about a different approach. Can you hardcode the SolarEdge DNS servers it's using?
If not try adding a port forward on the LAN for DNS traffic from the solaredge to some other DNS server. Maybe 8.8.8.8 or even run DNSmasq on another port and forward to that.
Steve
-
Hmm, weird that it happens after 3 days… Like maybe it's cached something and only has to re-resolve it then.
How about a different approach. Can you hardcode the SolarEdge DNS servers it's using?
If not try adding a port forward on the LAN for DNS traffic from the solaredge to some other DNS server. Maybe 8.8.8.8 or even run DNSmasq on another port and forward to that.
Steve
I should have a look, but i think its possible to enter the DNS in the solaredge invertor , i'll give the google DNS a try then
hope that would solve this problem -
At the moment i'am getting crazy of this .
I disabled DNSBL for some days now,and today again the SE invertor stops sending data to toe SE portal :(
What should be the best way to troubleshoot is ?( If i reboot PFsense, its working fine for a few days )
-
Check out the DHCP log.
By default, DHCP is activated on the SE.
Can you see the renewal dropping in every x time ?Instruct the DHCP server on pfSense that it will always give the same IP to your SE.
Then, pfSense => System => Routing => Gateway and add a line - ( "Gateway" will be the IP of your SE - don't check any boxes).Now you have a graph ( Status => Monitoring and select Quality).
-
Check out the DHCP log.
By default, DHCP is activated on the SE.
Can you see the renewal dropping in every x time ?Instruct the DHCP server on pfSense that it will always give the same IP to your SE.
Then, pfSense => System => Routing => Gateway and add a line - ( "Gateway" will be the IP of your SE - don't check any boxes).Now you have a graph ( Status => Monitoring and select Quality).
Done, lets wait for now
-
ok the drop / connection loss is there again , see the graph :
what's the next best thing to check ?
-
Nobody with some tips / hints ?
-
-
Wow so the inverter just starts dropping packets after a few hours?
It could be uploading data at that point I guess. Did that happen at the same time it lost connection?
Does anything else restore the connection besides rebooting pfSense? Physically disconnecting the inverter Ethernet cable for example? Or rebooting the inverter (if you can do that)?
Did the dhcp log show anything when it failed?
We need to determine what the actual disconnect is when it fails. What diagnostics do you have on the inverter? Were you able to hardcode anything?
Steve
-
Wow so the inverter just starts dropping packets after a few hours?
I think this is becauase the invertor stops sending packages when its in "night" mode
It could be uploading data at that point I guess. Did that happen at the same time it lost connection?
i really don't know , have to look for a way to monitor / check that
Does anything else restore the connection besides rebooting pfSense? Physically disconnecting the inverter Ethernet cable for example? Or rebooting the inverter (if you can do that)?
I just played around a few days ago on the invertor itself , to setup de DNS in the invertor manually and after i pressed some buttons en changed this DNS the connection if back agian( till yesterday)
Did the dhcp log show anything when it failed?
Getting this kind of log entery's :
We need to determine what the actual disconnect is when it fails. What diagnostics do you have on the inverter? Were you able to hardcode anything?
i can "hardcode"the IP / gateway / DNS , the website where its talking to , now: prod2.solaredge.com , and the connection itself : WiFi / Etherne etc.
Here's the most recent graph from the PF monitoring
-
What can i do ?
Today i had to reboot PFSense again, because of the connection between de invertor and the portal is gone ;( -
The only idea that comes to my mind is to monitor the traffic from the solaredge device with something like wireshark on a dump switch with something like a raspberry.
I have a solaredge device running which does not show any problems till now.
From the thread I have not seen if
- the se stops sending
- the portal refuses to receive
- pfsense is blocking.
(but I may have overlooked it)
RegardsHagen
-
@hbauer: and what is the configuration of you pfsense ( incl pfblockerNG etc ?
-
I have nothing special and no pfblocker. I just wanted to advice to try it without pfblocker. I have not seen in the thread the information that this was already tested. Sorry if I overlooked that.
-
still unsolved, and had to reboot PFSense every 3 day's .
After the reboot everything is running fine for the next 3 days ;(
So what could be the next step to troubleshoot this please ? -
@The:
So what could be the next step to troubleshoot this please ?
Get a real (as in someone who has an actual education in the field) network technican to do on location troubleshooting.
-
have you tried without pfblocker?
-
I recall I had a similar problem on my Solar Edge. Ultimately I did not have time to deal with the cable (Long 300ft run) and trouble-shooting, so I installed a TP-LINK Pharos system, basically a wifi point to point system, except I only used 1/2 of the system and pointed it towards my house, used the TP-Link gui to attach it to the wifi system in the house and it has worked flawlessly for a year now. You can buy the Pharos with 2.4 or 5GHZ, they are older units now but I just bought a backup unit (They normally come in pairs as they are designed to send point to point data from site a to site b and vice versa. Of course my inverters are located about 250 feet from the house on a solar array that is on a ground rack system. So basically you should be able to come out via cat5/6 cable to a wifi extender and make it work. Assuming that your connector is functioning correctly.
-
If you're still having this issue I would go back to a very basic setup. No pfBlocker, no other packages. Check again. One of those things must be causing this problem.
Steve
-
This post is deleted!
