From: Kev on 27 Feb 2007 15:09 Jeff Liebermann wrote: > Linksys also has an awful SNMP trap receiver at: > <ftp://ftp.linksys.com/pub/utility/wap54g_logviewer.zip> > It's really crude, but should be sufficient for testing. > I think that is very similar to the one my cousin used, actually it was probably even more basic as I don't remember the "Buttons".
From: Jeff Liebermann on 27 Feb 2007 21:32 On Tue, 27 Feb 2007 20:09:13 +0000, Kev <invalid(a)invalid.invalid> wrote: >Jeff Liebermann wrote: > >> Linksys also has an awful SNMP trap receiver at: >> <ftp://ftp.linksys.com/pub/utility/wap54g_logviewer.zip> >> It's really crude, but should be sufficient for testing. >I think that is very similar to the one my cousin used, actually it was >probably even more basic as I don't remember the "Buttons". Buttons? Egad's... it is a new version even though it's labeled v1.0. Looks somewhat less disgusting than the previous version. I tried sending it some traps with NET-SNMP but couldn't get anything to appear in the logs. I was able to see URL's (in SNMP traps) sent by a BEFW11S4v4 router, which should be similar to the WAP54G. I can also see URL's using SNMPUTIL as in: snmputil trap However, one needs to first configure SNMP on the machine that's running the SNMPUTIL program. Once installed, you can also run: evntwin evntcmd to send traps from the events log. See: <http://www.securityfocus.com/infocus/1301> Unfortunately, like almost all diagnostics from Microsoft, this one is also slightly broken: <http://support.microsoft.com/kb/q284255/> -- # Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060 # 831-336-2558 jeffl(a)comix.santa-cruz.ca.us # http://802.11junk.com jeffl(a)cruzio.com # http://www.LearnByDestroying.com AE6KS
From: Kev on 28 Feb 2007 05:18 Jeff Liebermann wrote: > On Tue, 27 Feb 2007 20:09:13 +0000, Kev <invalid(a)invalid.invalid> > wrote: > >> Jeff Liebermann wrote: >> >>> Linksys also has an awful SNMP trap receiver at: >>> <ftp://ftp.linksys.com/pub/utility/wap54g_logviewer.zip> >>> It's really crude, but should be sufficient for testing. > >> I think that is very similar to the one my cousin used, actually it was >> probably even more basic as I don't remember the "Buttons". > > Buttons? I don't remember a toolbar with it's associated icons. > Egad's... it is a new version even though it's labeled v1.0. > Looks somewhat less disgusting than the previous version. > > I tried sending it some traps with NET-SNMP but couldn't get anything > to appear in the logs. I was able to see URL's (in SNMP traps) sent > by a BEFW11S4v4 router, which should be similar to the WAP54G. What s/ware version? http://www.dslreports.com/faq/2333
From: Marek Zawirski on 4 Mar 2007 13:04 > Kev <invalid(a)invalid.invalid> hath wroth: > >> ZaWiR wrote: >>> Hello! >>> I've got problem with logging my AP activity to remote host. I'm >>> particulary interested in events such as positive clients attachments to >>> Access Point. My AP is Linksys WAP54G v3 EU, firmware 3.05. >>> >>> Web interface log window displays entries like: "Wireless PC connected >>> 00:13:02:XX:XX:XX" - this is what I would like to log on remote host. >>> However, AP is only sending stop/start entries to syslog port: (received >>> via ng-syslog) >>> "Feb 25 20:01:31 192.168.1.2 syslogd started: BusyBox v0.60.0 >>> (2005.12.28-06:45+0000)" >>> "Feb 25 23:05:22 192.168.1.2 System log daemon exiting." > >> I presume from this that you have enabled logging, Log Tab, and set the >> logviewer IP address to 192.168.1.2 .What s/ware have you loaded onto >> 192.168.1.2 to enable viewing of the logs? > > See: > <http://www.linksysdata.com/ui/WAP54G/v3/3.01/Administration-Log.htm> > for the setting. > >> Jeff provided this link to the Linksys one:- >> http://svs.sv.funpic.de/index.php?option=com_content&task=view&id=1&Itemid=63 >> Have you tried it? > > Well, I screwed up again. The above log viewer MIGHT work even though > this Log Viewer does not show the WAP54G as supported. It uses SNMP > traps, which I wrongly thought the WAP54G does NOT support. Apparently > it does. > > Linksys also has an awful SNMP trap receiver at: > <ftp://ftp.linksys.com/pub/utility/wap54g_logviewer.zip> > It's really crude, but should be sufficient for testing. > > For Linux, just about any SNMP trap receiver will work. There's one > in NET-SNMP. > <http://www.die.net/doc/linux/man/man5/snmptrapd.conf.5.html> > > A syslog monitor will only show WPA54G startup events, even though > syslogd is apparently functioning inside the WAP54G. Lame... > >> Check "The Administation-Log Tab" in the manual. >> My cousin had an earlier version of this AP and used to do logging with it. > > I just checked the configs on: > <http://www.linksysdata.com/ui/> > and all the various WAP54G mutations have the log viewer feature. Well... what are you talking about?;) I've claimed that what I want to achieve is REMOTE logging. I've sniffed eth interface again, and there is NO syslog/snmp traffic (for sure) during clients connection. So this must be AP-only problem, not my logging software. I don't want to use web-based log viewer on AP (at least, I can download this page regularly by script). And there is no possibility and need for testing "log-viewers" for Windows as there is no useful mgmt traffic from AP. Answering directly: 192.168.1.1 is my server, not 192.168.1.2 (AP), and there is no "viewer" software on this machine, there is only "logging" software. Page about enabling logging - which was provided by you - concerns Linksys router, not AP. Is there any WAP54G firmware version which is known (tested) to provide working snmp or syslog implementation=that sends useful information? Have you seen snmp traps or useful syslog entries on your eyes?:) Not my eyes yet... Best Regards, Marek Zawirski / zawir
First
|
Prev
|
Pages: 1 2 Prev: Fry's cheapie: Airlink AWL5025 $15 Next: funny linksys firmware rev/dates on WRT54G |