Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[terminlman]

I have seen lots of posts asking for help getting the router to email the log, but no definitive responses (for any of the different models mentioned.)  In my case, I have a DIR-651, Hardware Version: A2,  Firmware Version: 1.10NA.  I have tried all sorts of combinations of from/to address (including them being the same and being different) but always get a failure message in the log.  I'm on AT&T/Yahoo and have tried both smtp.att.yahoo.net and outbound.att.net, and ports 25, 465, and 587.  (Those are from memory - so might be wrong.)

Has anyone succeeded in having a DLink router email the logs using AT&T SMTP? 

Is it possible (as was suggested in one post, but with no follow-up) that it might be that the router simply does not have the correct security/encryption protocol required by the server.  (TLS?) 

At some point, I will examing the GPL released firmware code, but it may be a while until I have the time to dig through it.  Until then, I'd love to know if it is possible, or if I should just  give up.

As an alternative approach - is it possible for the router to send to an SMTP server on the LAN side?  I don't currently run one, but could easily install one just to receive the logs.  Might it be possible to send them to my own WAN address (DDNS) and port forward the connection in?

Thanks for any thoughts on this.

Jack

[FurryNutz]

See it where TLS authenticaion is on the ISP email system and some of these routers don't handle the TLS authentication feature correctly or not at all. My ISP didn't have this until they went to a google based email system then my logs topped working. 

[terminlman]

Then that's likely the issue.  Do you know if DLink has added TLS authentication to any of their current routers?  Is so, it might (eventually) be possible to back port it to the GPL version of the firmware for older models.

[FurryNutz]

I'll check my 868L and see...

[FurryNutz]

ya, it's not working on the 868L...There are two different SMTP ports for my ISP, I tried both and there not working...

I see Logs Sent in the router logs however no other status if the attempt failed or not.
This is my ISPs mail configuration:
https://support.google.com/mail/answer/13287?hl=en&ref_topic=2769079

[terminlman]

Well, in the DIR-651, the check box is just "enable authentication" which may amount to no more than name/password on unprotected port 25, so neither SSL nor TLS will work.  If that's true, then there are only two options I see.

1) play with the GPL source of the FW and add authentication.  I don't expect to have that set up and have time to play with it for at least a few weeks, but I'll definitely post back on what I find.

2) I'm going to assume that the router will only send email out on the WAN side.  That means it might be possible to send to your own WAN address and port forward 25 (or something else for at least a bit of security through obscurity) to an SMTP server on your LAN.  I'm not sure how much of an issue it would be to secure it sufficiently, but if it is set to receive only (and deliver to local mailbox) and not to send, then at least you know it can't be used to relay spam, which is what I'd worry about.  I'd like to try that, but I don't think I'll get to it any sooner than to the other.

[FurryNutz]

Any status on this? 

[terminlman]

I have not tried running my own smtp server yet.  I finally got CentOS installed in a VirtualBox environment, but it looks like the entire toolchain for creating firmware is 32 bit only (even though it cross-compiles) and will not run in a 64 bit OS, so I've probably got to reinstall the 32 bit CentOS instead.  I'm also wondering if I really need to use the version 5 instead of the latest 6 of CentOS.

[FurryNutz]

Keep us posted on how it goes. 

[terminlman]

quick update only - I don't think I need to install the 32bit CentOS.  I just needed to install the 32bit version of some packages (glibc so far, I'll have to see if it also needs any others).  I'll update once the build completes.  I'm hoping it will create a fw identical to the official 1.10, although I can imagine some differences, so I'm not sure how easy it will be to confirm that the build went correctly, short of actually trying it.