No email logs from Linksys WAG54G
Posted: Sun Oct 10, 2004 8:50 am
Hello,
I've just bought a Linksys WAG54G after my Netgear router stopped dishing out IP addresses via DHCP.
Anyway, I've enabled the email logs, given my server's SMTP address, a to: address and a from: address and I've not received a thing from the router. I've tried to provoke it to send me a log by forcing several scans on the Symantec security site, but nothing.
My SMTP server requires a username and password to log in - there's no space for this on the WAG54G's setup pages and Linksys support tell me that the router has a built-in SMTP service and should email these logs to an email address that I provide. I'd like to think it did - I think they're getting mixed up with the built-in SNMP service!
Has anybody managed to get this working? If so, how? And what's the trigger to send an email, as there are no schedules, unlike the Netgear routers.
Any info would be great.
I'm using the firmware version that came with the router (1.01.6) and can't see anything later that addresses this.
Thanks,
Matt
I've just bought a Linksys WAG54G after my Netgear router stopped dishing out IP addresses via DHCP.
Anyway, I've enabled the email logs, given my server's SMTP address, a to: address and a from: address and I've not received a thing from the router. I've tried to provoke it to send me a log by forcing several scans on the Symantec security site, but nothing.
My SMTP server requires a username and password to log in - there's no space for this on the WAG54G's setup pages and Linksys support tell me that the router has a built-in SMTP service and should email these logs to an email address that I provide. I'd like to think it did - I think they're getting mixed up with the built-in SNMP service!
Has anybody managed to get this working? If so, how? And what's the trigger to send an email, as there are no schedules, unlike the Netgear routers.
Any info would be great.
I'm using the firmware version that came with the router (1.01.6) and can't see anything later that addresses this.
Thanks,
Matt