Recent content by Homerz

I also discovered that Netgear apparently now provide the source code to their routers (in compliance with the GPL) here: http://kbserver.netgear.com/kb_web_files/n101238.asp Should be easy enough to "diff" the sources to find exactly what they changed to fix this issue, for those interested...

It's fixed!!! Incredible! http://kbserver.netgear.com/release_notes/D103204.asp Wow, it only took them ... what ... three years.

Yeah, mine's the "GT" model, with 108Mb/s WiFi, Router, and 4 port wired switch, all in one. AFAIK that is the latest firmware. <sigh> Oh well, time to turn off Email notification for another six months, I s'pose.

V1.02.09 (DG834GT), which was released earlier this month.

Oh well - it didn't work. In fact not only does it send the email with the date one month in the future, but now it sends it twice!

131.107.1.10 is the Microsoft Time Server. Bizarre that this should work where others do not! I have heard (although I can't remember the details) something about Microsoft using a non-standard NTP protocol on their servers. Could it be that this router uses those same (wrong) standards, and...

This is a followup to the old (closed) thread here: http://www.tek-tips.com/viewthread.cfm?qid=1260072 Well it's that time of year again folks. Each July, we Netgear DG834 owners "celebrate" our b0rken routers with syslogs emailed with corrupt date headers. As predicted, mine re-started this...

You have the "PN", whereas I have the "GT" version, so the firmware is probably incompatible, (mine is V1.02.04). Pity, or I would have asked for a copy of yours. Bear in mind, none of us are experiencing the date problem right now, due the New Year. Wait 'till July/August and see what...

I'm looking for a new router anyway. The DG834GT overheats far too easily, suffers from "freezing", i.e. unresponsive admin web interface, has a crap a wireless signal, and looks far too much like a kitchen appliance. Time I moved up to something a bit more professional.

MeToo® However, IIRC it wasn't until the middle of the year (July/August) that this started happening, so don't breath a sigh of relief just yet. Also, this now means that Netgear Tech. Supp. are even less motivated to investigate this, let alone fix it. Not that they ever seemed interested in...

Bet you a fiver that you'll just end up getting a bot generated reply like: "The case has been escalated to the relevant department and the issue is being looked into, there may shortly be a firmware release which solves this problem, please periodically visit our website to check for the...

OK so manually sending the log file works, and has the correct date: smtpc -m text/plain -s "NETGEAR Security Log [53:73:9F]" -r <xxxx>@<xxxx>.com -h <xxxx>.com -v </var/log/messages However, sending logs from the webpage, or allowing crond to send at preset times, results in a malformed date...

If you look at the available options for smtpc, you'll see that there is no way to specify a date (this is normal ... smtp gets its date from the system clock), so that leaves two possibilities. Either the system clock is wrong, or smtpc is receiving malformed data which subsequently corrupts...

<CTRL>d terminates and sends the message. It's a UNIX thang :)

Getting closer... The radio button (on the "Logs" page of the router) labeled "Send Log" runs this javascript function: function sendLog() { if(! is_email_on()) return; stdAction(document.forms[0],'sendlog'); } The stdAction() function is part of an external javascript called linux.js...