First let me say hello, and thanks to all who contribute here. I've been lurking for awhile now and this board was a major factor in my purchase of the M1. I hope I will be able to add to it as my own experiences grow.
Now to my problem. I am maybe 60% complete on my install with the control mounted, powered, and communicating with RP via an M1EP. Everything went without a hitch until I tried to set up and send email notifications. To drill it down to where I am now, it appears that anytime an attempt is made, the XEP goes through a reboot. All lights cycle off, then proceed to come back in a sequence that looks like the unit was just plugged in, or forced to reboot from RP. This occurs whether the test email button is used, or I write a rule to send email every couple of minutes.
I flashed or re-flashed all the devices, confirmed router firmware is up to date, put the XEP in the routers DMZ to be sure my lack of network knowledge on port forwarding wasn’t the issue, etc. Elk support suggested I needed to get an ip address for Verizons dns server, rather than allowing the router to resolve as it does for the rest of the LAN. This was done, without producing any change. I then put in the actual IP address of my mail server, so that as I understand it, no DNS server is needed. Also let me note here that while the time server test says it passes, I show no network traffic. And when I test the dynamic DNS, it fails the same as if sending email. After much hair pulling and staying up way too late the last couple of nights I have run across this post here.
It seems to describe the exact problems I am observing. It ends with stating that actiontec corrected the issues, however Verizon is now using a westell 9100EM router with their installations here. Is it possible this is round two with FIOS – XEP issues? Has anyone managed to get email working with this router on FIOS, or come up with a work around? I still have my old actiontec acting as a MOCA bridge for a desktop, so I could connect it to a coax that existed. Perhaps a more savvy network god could tell me if I connected the XEP to the actiontec if that would just be passing through and having the same issues, or might result in success. It’s awfully hot here in FL for another attic crawl, plus I would like to rule out other possibilities prior to releasing the lease on the new gear to use the actiontec as my gateway. (I like them replacing the equipment on a failure.)
My experience so far has me very impressed with ELK, but as I have no home phone and would prefer not to go cellular on this, I would be disappointed if there is no way for me to access the internet for reporting, or the ELK remotely, as that was the plan from day one. Any insight or suggestions are greatly appreciated.
Now to my problem. I am maybe 60% complete on my install with the control mounted, powered, and communicating with RP via an M1EP. Everything went without a hitch until I tried to set up and send email notifications. To drill it down to where I am now, it appears that anytime an attempt is made, the XEP goes through a reboot. All lights cycle off, then proceed to come back in a sequence that looks like the unit was just plugged in, or forced to reboot from RP. This occurs whether the test email button is used, or I write a rule to send email every couple of minutes.
I flashed or re-flashed all the devices, confirmed router firmware is up to date, put the XEP in the routers DMZ to be sure my lack of network knowledge on port forwarding wasn’t the issue, etc. Elk support suggested I needed to get an ip address for Verizons dns server, rather than allowing the router to resolve as it does for the rest of the LAN. This was done, without producing any change. I then put in the actual IP address of my mail server, so that as I understand it, no DNS server is needed. Also let me note here that while the time server test says it passes, I show no network traffic. And when I test the dynamic DNS, it fails the same as if sending email. After much hair pulling and staying up way too late the last couple of nights I have run across this post here.
It seems to describe the exact problems I am observing. It ends with stating that actiontec corrected the issues, however Verizon is now using a westell 9100EM router with their installations here. Is it possible this is round two with FIOS – XEP issues? Has anyone managed to get email working with this router on FIOS, or come up with a work around? I still have my old actiontec acting as a MOCA bridge for a desktop, so I could connect it to a coax that existed. Perhaps a more savvy network god could tell me if I connected the XEP to the actiontec if that would just be passing through and having the same issues, or might result in success. It’s awfully hot here in FL for another attic crawl, plus I would like to rule out other possibilities prior to releasing the lease on the new gear to use the actiontec as my gateway. (I like them replacing the equipment on a failure.)
My experience so far has me very impressed with ELK, but as I have no home phone and would prefer not to go cellular on this, I would be disappointed if there is no way for me to access the internet for reporting, or the ELK remotely, as that was the plan from day one. Any insight or suggestions are greatly appreciated.