Cable Forum - View Single Post

greyhairbadger · 19-09-2011, 13:48

Hi all,

I am new to the forums, apologies if this is posted in the wrong place. May I pick your collective brains please?

I have a LAN consisting of a 192.168.1.1/24. A linux server runs the rsyslog daemon listening on port 514.

My router generates copious amounts of log. In lieu of storing this internally, it squirts the data at my server through UDP. The server fields the data and appends it to a text file on a network share. All pretty standard.

My cable modem also generates an event log, however it only seems to be capable of storing and displaying 32 lines internally. (This is currently full of UCD changes, presumably flirting with QAM16 before dropping back to QPSK.) The cable modem appears to be transparent. The diagnostic pages are available at 192.168.100.1, which is naturally outside of my subnet.

My question is this: Is there any easy way the cable modem can be persuaded to log remotely? And even if it can, is there any way to aim it at my server through the NAT router? The server is not internet-facing, and I prefer it to stay that way.

I welcome any thoughts or insights.

thanks in advance,

Phil.

19-09-2011, 13:48	#1
greyhairbadger Inactive Join Date: Sep 2011 Location: Birmingham, England Services: Virgin Media HFC broadband Posts: 17	Ambit 256 SOCM Event Log Hi all, I am new to the forums, apologies if this is posted in the wrong place. May I pick your collective brains please? I have a LAN consisting of a 192.168.1.1/24. A linux server runs the rsyslog daemon listening on port 514. My router generates copious amounts of log. In lieu of storing this internally, it squirts the data at my server through UDP. The server fields the data and appends it to a text file on a network share. All pretty standard. My cable modem also generates an event log, however it only seems to be capable of storing and displaying 32 lines internally. (This is currently full of UCD changes, presumably flirting with QAM16 before dropping back to QPSK.) The cable modem appears to be transparent. The diagnostic pages are available at 192.168.100.1, which is naturally outside of my subnet. My question is this: Is there any easy way the cable modem can be persuaded to log remotely? And even if it can, is there any way to aim it at my server through the NAT router? The server is not internet-facing, and I prefer it to stay that way. I welcome any thoughts or insights. thanks in advance, Phil.